On Wed, Dec 19, 2007 at 11:53:52AM +0100, Lionel Cons wrote:
> I've started a scan against a list of machines identified by their IP
> addresses. The Nmap process takes 100% CPU and is stuck in the name
> resolution part. I killed it after 25 minutes, which is a lot to
> resolve only 400+ addresses.
>
> Here are the last lines printed:
>
> [...]
> We got a TCP ping packet back from 192.168.74.73 port 80 (trynum = 1)
> We got a TCP ping packet back from 192.168.73.75 port 80 (trynum = 1)
> We got a TCP ping packet back from 192.168.21.207 port 80 (trynum = 1)
> We got a ping packet back from 192.168.45.7: id = 48978 seq = 0 checksum = 16557
> Completed Ping Scan at 11:20, 1.84s elapsed (436 total hosts)
> mass_rdns: Using DNS server 192.168.1.5
> mass_rdns: Using DNS server 192.168.1.6
> Initiating Parallel DNS resolution of 436 hosts. at 11:20
Thanks for the report Lionel. Can you run it with "--packet-trace
-d5" and see what happens? After it runs for 20 minutes or so, kill
it with ^C. Then would you grab the last 500 lines or so and send
them to the list? That should help us understand where it is looping.
Thanks,
-F
_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org
Received on Dec 20 2007
Intro
