• Subject: Re: 5394 and V.35 lines
  • From: "Lou Schmaus" <lschmaus@xxxxxxxx>
  • Date: Thu, 2 Nov 2000 16:18:48 -0500

All,

The 5394 is up and humming. As it turns out, the problem was a bad V.35
connector on the pigtail cable from the controller to the CSU/DSU. As soon
as we swapped the cable from another 5394 that we took down to test cables,
lights started flashing like crazy in the CSU/DSU, and sign-on screens
started popping up, paper started spitting out of printers, people were
dancing in the aisles! Hopefully I didn't sound too smug when I called the
software vendor, who assured us that there couldn't be a hardware problem.

Who the heck came up with the connector for the V.35 interface? What a pain!
It takes three hands just to screw the connector on.

Well, thanks again to everyone on the list who helped!


Lou Schmaus
CCA, Inc.
Jackson, NJ 08527
lschmaus@link400.com


----- Original Message -----
From: "Chuck Lewis" <clewis@iquest.net>
To: <MIDRANGE-L@midrange.com>
Sent: Thursday, November 02, 2000 11:30 AM
Subject: Re: 5394 and V.35 lines


> Lou,
>
> As I recall (and this was YEARS ago now) when we moved to V.35, there was
an
> upgrade that had to be done to the 5394's if they were before acertain
serial
> number range. This included a mother board replacement and more memory...
>
> Chuck


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact [javascript protected email address].