Re: NSE Windows Raw Socket Fatal Error for Non-Admin (or UAC is Enabled)

[Rob Nicholls <robert () robnicholls co uk>]

On 31.10.2012 17:05, David Fifield wrote:
> Thanks Rob. Please try r30160.

I tried r30168 (that'll teach me to use my own "makefile" batch file 
I've written to avoid installing cygwin), and that's stopped the fatal 
error occurring :D

When running Nmap without an elevated Command Prompt I now get:

Initiating NSE at 17:40
NSE: 'ipidseq' (thread: 03C55F50) against xx.xx.xx.xx threw an error!
C:\Program Files (x86)\Nmap/scripts\ipidseq.nse:213: failed to open raw
socket:
An attempt was made to access a socket in a way forbidden by its access
permissi
ons.  (errno 10013)
stack traceback:
         [C]: in function 'ip_open'
         C:\Program Files (x86)\Nmap/scripts\ipidseq.nse:213: in
function <C:\Program Files (x86)\Nmap/scripts\ipidseq.nse:204>
         (...tail calls...)

Completed NSE at 17:40, 0.01s elapsed

And when I use an elevated Command Prompt, I see:

Initiating NSE at 17:40
NSE: Finished 'ipidseq' (thread: 03B56910) against xx.xx.xx.xx.
Completed NSE at 17:40, 0.24s elapsed
Nmap scan report for xxx.xxxxxx.xxx (xx.xx.xx.xx)
Host is up, received user-set (0.018s latency).
Scanned at 2012-10-31 17:40:32 GMT Standard Time for 6s
PORT   STATE SERVICE REASON  VERSION
80/tcp open  http    syn-ack Microsoft HTTPAPI httpd 2.0 (SSDP/UPnP)
Service Info: OS: Windows; CPE: cpe:/o:microsoft:windows

Host script results:
|_ipidseq: Incremental! [used port 80]

I still find it odd that the first error message occurs unless I'm
running with an elevated Command Prompt. Sounds like another bug to me,
but at least I can workaround it for now, and if I forget it's not too
fatal.

Thanks!

Rob


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