Re: Nmap doesn't work on Vista Ultimate Edition

["Gianluca Varenni" <gianluca.varenni () gmail com>]

Easy way to test if it's a privilege problem: open a command line and type 
"net start npf". It's a privilege problem if it tells you "access denied".

Have a nice day
GV

----- Original Message ----- 
From: "Rob Nicholls" <robert () everythingeverything co uk>
To: <nmap-dev () insecure org>
Cc: <contact () absolom ro>
Sent: Tuesday, July 17, 2007 5:04 PM
Subject: Re: Nmap doesn't work on Vista Ultimate Edition


> I'm not sure if we'll ever have a "bugless version" of nmap (as great new
> features are added all the time), but it appears to be incredibly stable 
> and
> I'm very impressed with the latest 4.22SOC2.
>
> Assuming it's the same "old" issue, this was discussed back in February:
> http://seclists.org/nmap-dev/2007/q1/index.html#176
> Back then, Gianluca mentioned a registry tweak (that I use on Vista), 
> along
> with a good explanation as to why it's happening:
> http://seclists.org/nmap-dev/2007/q1/0195.html
>
> Even with UAC disabled, you still need to run nmap as an Admin user at 
> least
> once, so that nmap is able to load the WinPcap kernel driver into memory.
> Are you using a Standard user or Admin user account?
>
> The easy alternative (and what I've done on my Vista PCs [with UAC 
> enabled],
> although most of my testing is still performed with XP/Linux) is to make 
> the
> following change to the registry, which loads the WinPcap driver into 
> memory
> at startup, so that Standard users can use it from the very start (this is
> also useful if UAC is enabled and you're an Admin, as it saves you from
> having to initially bring up an elevated "Command Prompt"):
>
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NPF\Start
>
> Change the value to 2 (instead of the default of 3), and reboot Vista.
>
> BTW I'm assuming you have WinPcap 4.x installed, and the latest stable (or
> newer) version of nmap. The "error" is not technically a bug in nmap or
> WinPcap, but the error message isn't particularly clear that it's 
> (possibly)
> a privilege problem. Hopefully that'll resolve the issue you're seeing.
>
> Regards,
>
> Rob Nicholls
>
>
>
> _______________________________________________
> Sent through the nmap-dev mailing list
> http://cgi.insecure.org/mailman/listinfo/nmap-dev
> Archived at http://SecLists.Org 


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