Re: win32 - failed to determine dst mac address for target - i wanna help

[kx <kxmail () gmail com>]

Can you please email me you nmap --iflist output, and you ipconfig
/all output for every host?

Then can you describe in explain words your LAN setup? That is, how
are the hosts connected together and to the internet?  No need for any
public IP addresses, and please mask any addresses you are sensitive
about, just be consistent, e.g. 192.168.1.1 becomes aaa.xxx.1.1 and
192.168.1.100 become aaa.xxx.1.100 but 10.1.1.1 becomes bbb.xxx.1.1.

I've looked at this before and we had issues with people trying to
scan over PPP adapters (Fyodor fixed the error message), and some
issues where people had botched routing tables like no gateway for the
target address and no default gateway (I don't believe we added better
error messages).

Hopefully I can help.  However, as I haven't been able to recreate
this, maybe you could look at this thread

http://seclists.org/lists/nmap-dev/2005/Oct-Dec/0108.html

and this guide

http://www.insecure.org/nmap/install/inst-windows.html#inst-win-source

To learn how to compile nmap for free on windows. This way we can at
least put in some breaks to inspect the call stack as well as inspect
a few variables values.

Cheers,
  kx




On 3/14/06, Louie Jagoe <jagoe () stnoble com> wrote:
> Hiya,
>
> I have the perfect test environment for helping to troubleshoot this
> "failed to determine dst mac address for target" problem. There seem to
> be a number of people (guaged by googling) having this problem (and I'm
> one of them) so I'd like to help solving it. (Just for the record, I
> have researched this problem in forums, newsgroups and on the web so I
> don't believe I'm overlooking the obvious or re-inventing the wheel.)
>
> Basically I have three machines in the test bed, one of which works
> perfectly:
>
>        machine #1 - Toshiba Tecra 9100, winxp pro, sp2, fully patched
>
>        machine #2 - Dell Dimension 8400, winxp pro, sp2, fully patched
>
>        machine #3 - (old) Dell Precision workstation, win2k, sp4, fully
> patched
>
>
> All machines have winpcap 3.1 and the microsoft network monitor driver
> installed. They all have no trouble running snort. The nmap distros on
> these machines are all downloaded w32 binaries.
>
> Machine #1 works fine with nmap-3.81, nmap-3.93, nmap-4.01 and
> nmap-4.02Alpha2.
>
> Machine #2 (same os and patch set as machine #1) with nmap-4.01 gives
> the dreaded "failed to determine dst mac address for target" only when
> trying to scan hosts outside of its network segment (i.e. layer 2 across
> a router). In other words, nmap works fine on the home lan.
>
> Machine #3 (different os altogether) with nmap-4.01 gives exactly the
> same behaviour as machine #2
>
> Preliminary comparison of registry settings yielded nothing useful. The
> windows xp firewall has also been ruled out. So from where I sit I have
> the perfect lab environment for patch testing. I don't have the time to
> roll up my sleeves and get into the source (it would take me a month
> just to get up to speed again on vc++ and tcp/ip programming). But I can
> offer my services on a sys/network admin level and try out patches or
> config suggestions.
>
> I wasn't sure that the nmap dev list was such a good starting point,
> thus the reason for this email.
>
> Please advise,
>
> Louie
>
> =====================================================
> Louis Jagoe, Director
> St. Noble Company                 Geneva's IT Experts
> Geneva, Switzerland            http://www.stnoble.com
> =====================================================
>
>
> _______________________________________________
> Sent through the nmap-dev mailing list
> http://cgi.insecure.org/mailman/listinfo/nmap-dev


_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev