Re: Nmap on Windows 2000

["DePriest, Jason R." <jrdepriest () gmail com>]

I run nmap 5.35DC1 on a Windows 2000 Professional jumpbox.

Originally, this was to avoid the raw sockets limitations introduced with
Windows XP SP2.

I know that nmap has worked around this issue, but I never upgraded my box.
It's hard to upgrade since it's a six hour drive away from where I work and
sits in a personnel-free lab.

Does this mean that the next official binary release won't work on my
Windows 2000 Pro box?  That would be give an incentive to replace it or
upgrade it.

-Jason

On Nov 17, 2010 2:30 PM, "Rob Nicholls" <robert () robnicholls co uk> wrote:

I know we've made an effort in the past to support Nmap on Windows 2000, but
it seems that Microsoft aren't willing to support older (unsupported) OS
with Visual C++ 2010, which we're now using to build Nmap, Ncat and Nping.

http://www.microsoft.com/downloads/en/details.aspx?familyid=A7B7A05E-6DE6-4D
3A-A423-37BF0912DB84<http://www.microsoft.com/downloads/en/details.aspx?familyid=A7B7A05E-6DE6-4D3A-A423-37BF0912DB84>

Windows XP SP3 and Server 2003 SP2 are apparently the earliest OS that are
supported. The vcredist_x86.exe installer fails when I tried it on a fully
patched Windows 2000 Professional VM (I've not tried it on XP SP2, if it
does fail and requires SP3 then I suspect it's down to a policy decision
rather than technical reason). It tried to extract the files and then 2000
complains:

"Extract Failed"
"is not a valid Win32 application"

I haven't managed to quickly identify a way of getting the installer to
work.

I also had Zenmap crash on startup, although that could be down to my Python
build environment; I've not tried an official installer yet.

Is now a good time to (finally) officially drop support for Windows 2000,
and try to update all of the Nmap documentation?

Rob


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