Hello!
Just downloaded the latest nmapwin and install it on a
win2k SP2. No problems at all as far as the installation,
the installer install even a shortcut to my desktop. After I
reboot my machine, I launched the nmapwin by double
clicking on the shortcut icon and the GUI came up fine.
Before I was able to do anything -- my IDS system
started to go nuts -- the logs shown that my machine
was trying to scan 10.10.10.0/24 Again, I did not
configure anything ousing the GUI interface of the
nampwin. where the nmap is getting its arguments to
perform a scan on 10.10.10.0/24
this is occuring every time that the winmap shortcut is
executed. does the argument already embedded in the
nmapsrv? Is this a bug? or something I did not configure
on my end..
Please let me know.
TIA
Logged In: YES
user_id=545266
This (stupid) bug has been fixed in v1.2.13...