Article View: comp.sources.bugs
Article #663*unable to connect*
From: Donna Cummings
Date: Fri, 18 Dec 1992 02:51
Date: Fri, 18 Dec 1992 02:51
6 lines
1100 bytes
1100 bytes
Why are we constantly getting *unable to connect* messages, or *connection refused* when the Mud is not down...it is a problem on our side? Are our links bad? I know very little..but if it is our server or links that are the problem, when can we expect them to be improved..? I am getting more and more impatient, today I was not able to connect with IRC..I dont use it, wanted to test and see if I could. Message *unable to connect* came back for EVERY server. Please leave me private mail on this...would lik e to hear from someone in charge of telnet/mud/etc. connections. Dont know if you have anyone like that..but please let me know why our service is so bad. Donna Cummings
Technical Details
Message-ID:
<1992Dec18.025138.9820@netcom.com>Path:
arc1-ca.pugleaf.net!sparky!uunet!spool.mu.edu!umn.edu!csus.edu!netcom.com!taliaShow Full Headers
Complete Article Headers
Newsgroups: comp.sources.bugs,comp.sources.bugs Path: arc1-ca.pugleaf.net!sparky!uunet!spool.mu.edu!umn.edu!csus.edu!netcom.com!talia From: talia@netcom.com (Donna Cummings) Subject: *unable to connect* Message-ID: <1992Dec18.025138.9820@netcom.com> Followup-To: poster Keywords: Server problems Organization: Netcom - Online Communication Services (408 241-9760 guest) Date: Fri, 18 Dec 1992 02:51:38 GMT Lines: 6