Ping Problem with Nmap 5.20 (machine specific).

[Ben Dalling <b.dalling () locp co uk>]

Hi,

Just to clarify, this problem is only affecting the machine that we use
for carrying out regular Nmap scans on our network.  Nmap 5.20 works fine
on other nodes within our network and this is a problem specific to the
machine I'm using.

The machine in question is a virtual machine running on top of VMware
ESX.  The guest OS of the virtual machine is Red Hat Enterprise Server
5.4.  When I run Nmap 5.20 it doesn't see any remote machines (see output
below).  When I reinstall Nmap 5.00 everything works OK again.

Has anyone got any ideas why this particular machine isn't getting on with
the new version of Nmap?

*** Sample output ***
# nmap -sS -sU -A foobar

Starting Nmap 5.20 ( http://nmap.org ) at 2010-01-27 08:05 GMT
Note: Host seems down. If it is really up, but blocking our ping probes, try -PN
Nmap done: 1 IP address (0 hosts up) scanned in 0.60 seconds
# nmap -sS -sU -A -PN foobar

Starting Nmap 5.20 ( http://nmap.org ) at 2010-01-27 08:05 GMT
Nmap done: 1 IP address (0 hosts up) scanned in 0.60 seconds
# ping -c 1 foobar
PING foobar (10.201.228.46) 56(84) bytes of data.
64 bytes from foobar (10.201.228.46): icmp_seq=1 ttl=64 time=0.257 ms

--- foobar ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.257/0.257/0.257/0.000 ms
*** End of sample output ***

Best regards,
-- 
Ben Dalling
email: b.dalling () locp co uk
www: http://www.locp.co.uk
_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://seclists.org/nmap-dev/