NMAP scans using 100% CPU

(imported topic written by jreinec1)

I have problems with running some NMAP scans. Basically, the CPU of the machine doing the scanning will sit at 100% CPU utilization indefinately while the network utilization is idle. What log file can I look at to see what IP may be hanging the scan? I have had this happen using the wizard to scan the local subnet and a range of addresses. Sometimes I can run it a second time and it will work. I have had the issue with multiple computers doing the scanning. Some with XP and some with 2003 server OS.

(imported comment written by rharmer91)

bump

(imported comment written by BenKus)

The issue you mentioned sounds like it might be related to another issue we have seen and reported to NMAP:

http://seclists.org/nmap-dev/2008/q2/0088.html

Can anyone confirm if it seems to be related to scanning a Mac?

Ben