RE: Most final release candidate yet: Nmap 4.49RC6

["Rob Nicholls" <robert () everythingeverything co uk>]

Morning,

> For information, I have following bug with Nmap 4.49RC6.
>
> - If I use Ethernet + DHCP, everything works OK.
> - If I use Ethernet + fixed IP address:

That's a bit odd, because it works fine for me with a static IP :S

I spent two weeks last month hopping around several networks and dozens of
vlans using a whole series of static IP addresses (the UAC prompt that
appears when you change your IP address did finally start to get
annoying), using one of the 4.22SOC versions IIRC, which should be pretty
similar to RC6. And I've just tried RC6 using a static IP against a couple
of servers (one plugged into the same switch, the other is 9 hops away
across the internet) without noticing any problems.

Fred, have you got UAC disabled? If not, do you have any more luck if you
use an elevated Command Prompt? It might help if you could provide the
outputs (when you're using a static and dynamic IP) from

nmap --iflist

I think the last time I saw the message you're seeing on Vista was when I
had UAC enabled and before I'd changed the registry setting so WinPcap was
already loaded*; but if Wireshark works fine then it suggests to me that
WinPcap might not be at fault (unless you're running Wireshark elevated,
but nmap should work fine after you've done that as the WinPcap driver
will already be successfully loaded for nmap to use).


Rob

* HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NPF\Start set to
the value 2 (instead of the default of 3)



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