> Windows has another bug; they don't include a proper loopback function
> with the standard distribution _and_ they have some asenine view that if
> there's no physical network connection available, they tear down the
> network stack! This means that anything that connects with TCP/IP can't
> work, even if it's to the local machine. I consider this idiocy, but,
> there's windows for you in a nutshell...
>
> However, you _can_ find a proper "loopback driver", I think they call it -
> software, of course. Also, I carry in my laptop case a special HARDWARE
> loopback connector! It's an RJ45 that has the wires crossed over. I use it
> when I'm at a customer site or otherwise "away from home" and my customer
> doesn't have the software loopback - plug my loopback connector into any
> "twisted pair ethernet" socket and suddenly the TCP/IP software works
> fine!
there is a loopback driver shipped with windows xp / windows 2003. but you
have to add it manually ("add hardwar"e --> "add a new hardware device" -->
"select from a list" --> "show all devices" --> "microsoft" --> "Microsoft
Loopback Adapter")
cheers,
thomas