Yeah, because Snopes is the ultimate bastion of truth. :rolleyes:

I hear crickets...

Don't like it. Too gray. Boring.

"Goosh it"? :confused:

Here you will find an enlightening counter-point. http://www.junkscience.com[^] One should always thoughtfully consider both sides of an argument.

Does anyone know whatever happened to Mathew Hall? He is the creator of two of the best works found on CP: XPTable[^] and XPExplorerBar[^]. He stopped posting replies for those two projects back in late 2005.:confused:

Win2k3 requires a listening socket to be bound to a specific IP, whereas Win2k and NT4 do not. We were not binding to a specific IP. One small change, and the code works on all 3 operating systems. Jon

I can't seem to open a listening socket on Windows Server 2003. The very same code has run on NT4 and Win2k for years. But when I try to run it on Win2k3, it fails to create a listening socket. The code is a C++ wrapper for the Windows Socket API (MFC Socket classes are mostly useless). I don't believe there is anything unusual about the way the code was implemented. It has never given us any trouble in the past. I guess my question is this: Is there something more that I must know/do in order to run a socket server (i.e. listening socket) on Win2k3. Is this part of MS's Secure Computing Initiative. Or am I just overlooking the obvious? Any help would be greatly appreciated. Thanks, Jon

Amen! Jon