Nmap Development mailing list archives

AW: --win_help


From: "Baumgart, Alexander (K-GOT-1)" <alexander.baumgart () volkswagen de>
Date: Mon, 19 Dec 2005 13:53:08 +0100


It sounds like if you have an active connection but an unplugged 
interface then you won't be able to reach the DNS servers at all (or 
even the targets)? Try using -n to disable reverse DNS queries 
entirely.


I'm guessing multiple NIC's, but windows tries to use the wrong one. 
This happens on my XP SP1 as well, although I can't say I'm surprised 
they haven't gotten to the "link up" stage yet...

Thx for all the help. Right in 3.90 --winhelp is gone, but --iflist do
likewise. My config is :

Starting Nmap 3.95 ( http://www.insecure.org/nmap ) at 2005-12-19 12:53
Westeuropõische Normalzeit
************************INTERFACES************************
DEV  (SHORT) IP/MASK            TYPE     UP MAC
eth0 (eth0)  10.33.56.221/24    ethernet up 00:0B:5D:24:7A:F7
eth1 (eth1)  192.168.120.254/24 ethernet up 00:07:77:64:09:32
lo0  (lo0)   127.0.0.1/8        loopback up

**************************ROUTES**************************
DST/MASK           DEV  GATEWAY
192.168.120.254/32 lo0  127.0.0.1
255.255.255.255/32 eth0 10.33.56.221
10.33.56.221/32    lo0  127.0.0.1
10.255.255.255/32  eth0 10.33.56.221
192.168.120.255/32 eth1 192.168.120.254
255.255.255.255/32 eth1 192.168.120.254
10.33.56.0/0       eth0 10.33.56.221
192.168.120.0/0    eth1 192.168.120.254
127.0.0.0/0        lo0  127.0.0.1
224.0.0.0/0        eth0 10.33.56.221
224.0.0.0/0        eth1 192.168.120.254
0.0.0.0/0          eth0 10.33.56.254

192.168.120.254 is a "AVM FRITZ!web PPP over ISDN", that make the trouble.
Its per default enable and unplugged.
If i disable it DNS work a usally. I tried to bind nmap to a specified
interface per

nmap -e eth0 -sP 10.33.56.0/24

Starting Nmap 3.95 ( http://www.insecure.org/nmap ) at 2005-12-19 13:45
Westeuropõische Normalzeit
NmapArpCache() can only take IPv4 addresses.  Sorry
QUITTING!

nmap -e lo0 -sP 10.33.56.0/24 

work as usally, what i also didnt understand. Its seem not to be a nmap
problem, its more strange behaviour under XP SP2.

Regards Baumgart


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


Current thread: