Home page logo
/

nmap-dev logo Nmap Development mailing list archives

Re: Win32 version of Nmap can't connect to host on Windows XP pro.
From: "Gisle Vanem" <giva () bgnett no>
Date: Sun, 1 Feb 2004 16:32:36 +0100

"John L Richardson" <JohnLRichardson () cox net> said:

Nmap works fine on both my linux and win2k machines.

There seems to be a problem with XP pro.

I have the optional XP network firewall disabled.

Has anyone tested the Win32 version of nmap.exe on XP pro?

Works fine here. It may be a problem with the order of devices.
Some libpcap programs (nmap included AFAICS) blindly uses the 
first interface only (which may be a IPv6 tunneling interface). 

Try
c:\>nmap --win_list_interfaces --win_trace
***WinIP***  initializing if tables
***WinIP***  if tables complete :)
***WinIP***  trying to initialize winpcap 2.1
***WinIP***  winpcap is present
***WinIP***  testing for raw sockets
***WinIP***  rawsock is available
***WinIP***  reading winpcap interface list
pcap device:  \Device\NPF_{93380695-0E31-456C-9EB0-8802E111C09D}
 result:       physaddr (0x0001800c70b2) matches eth0
pcap device:  \Device\NPF_{7F56352E-EF2F-49F4-844C-BA1FA0105667}
 result:      no match (physaddr = 0x020054554e01)
***WinIP***  o.isr00t = 1
Available interfaces:

Name        Raw send  Raw receive  IP
loopback0   SOCK_RAW  SOCK_RAW     127.0.0.1
eth0        SOCK_RAW  winpcap      10.0.0.6
----

which in my case happens to be the physical adapter first
(the "{93..}") and the MS tunnel adapter second.

Try some of the other '--win' options. Use "nmap --win_help"
to show them.

--gv



---------------------------------------------------------------------
For help using this (nmap-dev) mailing list, send a blank email to 
nmap-dev-help () insecure org . List archive: http://seclists.org



  By Date           By Thread  

Current thread:
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]
AlienVault