

A Microsoft Security Tools Web page links directly to Nmap (at the second URL below).
ADVANCED MCE REMOTE MAPPER DOWNLOAD
You can read more about or download Nmap at the Web site (at the first URL below). If you recall, Windows 95 doesn't support raw sockets either and Nmap runs on that platform, so there's a good chance that a workaround is possible for XP SP2. The IP source address for any outgoing UDP datagram must exist on a network interface or the datagram is dropped."įyodor is looking for a way around the problem, and a solution might have already been found by the time you read this newsletter. " - TCP data cannot be sent over raw sockets, UDP datagrams with invalid source addresses cannot be sent over raw sockets. However, the ability to send traffic over raw sockets has been restricted in two ways: Michael Howard, security program manager on the XP team, posted an interesting entry ("A little more info on raw sockets and Windows XP SP2," at the first URL below) to his blog that excerpts a portion of the Microsoft document "Changes to Functionality in Microsoft Windows XP SP2." The Microsoft document (at the second URL below) points out that "The Windows implementation of TCP/IP still supports receiving traffic on raw IP sockets. According to a message posted by Nmap author, Fyodor, on his Web site, someone from Microsoft stated that Microsoft changed raw socket operation because "the only apps using \ on XP were people writing attack tools." The reason is that in SP2, Microsoft changed the way raw sockets (which are used by Nmap) operate. If you're one of the countless network administrators who use the hugely popular Network Mapper (Nmap) network exploration and auditing tool, then you might already know that it doesn't work on Windows XP Service Pack 2 (SP2).
