DH> Turned out the problem was in the USA - the MSNET Domain
 DH> Name Server was down due to a local power outage
 DH> (presumably on the MicroSoft campus).  Implementing a
 DH> worldwide intended monopoly DNS without nobreak power

Trying to centralise an inherently distributed design was never gunna work :)

 DH> Why's this here?   This looked _exactly_ like a modem
 DH> protocol negotiation fault.  He could dial out, connect, it
 DH> would handshake partway, freeze, and a moment or two later,
 DH> disconnect.  Trace on WinSock finally brought out a clue,

Don't tell me .. they used ATS0=2 or so on 1000 modems?  Fidonet tech is
still streets ahead in plain modem / connectivity / cost minimisation
stakes, by and large, eh?

 DH> then a very aggrieved phone call on his part to some
 DH> luckless MS employee found the actual cause.  Took over an
 DH> hour to sweat through and identify.

 DH> Moral - it ain't always your own gear - even when it looks like it.

Que?  I thought it was _always_ the other end's gear, by definition! :)

Regards, Ian

--- MaltEd 1.0.b5