Re: NSE errors

[David Fifield <david () bamsoftware com>]

On Wed, Apr 10, 2013 at 09:44:56PM -0500, Christopher Clements wrote:
> Was able to reproduce, but I'm afraid I don't know enough about NSE's
> innards to understand why:
>
> NSOCK INFO [2586.2190s] nsock_trace_handler_callback(): Callback: WRITE SUCCESS for EID 50611 [172.16.0.2:500]
> NSE: UDP 192.168.0.1:839 > 172.16.0.2:500 | SEND
> NSOCK INFO [2586.2710s] nsock_readbytes(): Read request for 1 bytes from IOD #2251 [172.16.0.2:500] EID 50618
> NSOCK INFO [2586.5740s] nsock_trace_handler_callback(): Callback: READ TIMEOUT for EID 48922 [172.16.0.3:123]
> NSE: rpc-grind: isRPC didn't receive response.
> NSE: Target port 123 is not a RPC port.
> NSE: Finished 'rpc-grind' (thread: 0x5cbcb60) against 172.16.0.3:123.
> NSE: UDP 192.168.0.1:237 > 172.16.0.3:123 | CLOSE
> NSOCK INFO [2586.5800s] nsi_delete(): nsi_delete (IOD #2181)
> NSOCK INFO [2586.6330s] nsi_new2(): nsi_new (IOD #2252)
> NSOCK INFO [2586.6340s] nsock_connect_tcp(): TCP connection requested to 172.16.0.1:2002 (IOD #2252) EID 50624
> NSOCK ERROR [2586.6340s] nsock_make_socket(): Bind to 0.0.0.0 failed (IOD #2252): Address already in use
> NSOCK INFO [2586.6660s] nsock_trace_handler_callback(): Callback: CONNECT SUCCESS for EID 50624 [172.16.0.1:2002]
> NSE: TCP 192.168.0.1:46337 > 172.16.0.1:2002 | CONNECT
> NSE: TCP 192.168.0.1:46337 > 172.16.0.1:2002 | 00000000: 80 00 00 28 41 a2 5e 58 00 00 00 00 00 00 00 02    (A ^X
> 00000010: 00 01 86 a0 00 00 00 02 00 00 00 00 00 00 00 00
> 00000020: 00 00 00 00 00 00 00 00 00 00 00 00
>
> this was from a -d3 run.  I have the full run output if it would help.

What is the command line you used?

Please send me the full output, it will help. I'm trying to figure out
what script is trying to bind to 0.0.0.0 and send 44 bytes to port 2002.

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