RE: Client Access disconnecting

["Ray Peterson" <RayPeterson@xxxxxxxxx>]

You hit that nail on the head!  And your "tool name" does fit ;-)

The biggest problem we have is the fact that our data is transported as
"overhead" on the video network.  The existing network contracts expire in
2005 and will be replaced with something new.  We're pushing to have the
replacement be IP video over a DS-3(or better) based data network
(essentially internet-2).  We hope to have our first I2 link up later this
year to test the concept.

We've experienced a number of different CA/400 disconnect problems, but it
seems that the cause of the problem is different each time.  The pc's we put
on the desktop have so many software packages installed that it's amazing
any of it works.  Other times it's been a router or switch problem or the
various telco problems.   It'll be interesting to see if IBM can shed some
light on the problem.

Ray


-----Original Message-----
From: midrange-l-admin@midrange.com
[mailto:midrange-l-admin@midrange.com]On Behalf Of Reeve Fritchman
Sent: Friday, March 01, 2002 7:12 AM
To: midrange-l@midrange.com
Subject: RE: Client Access disconnecting


There's still a lot of "fix it with a hammer" thinking in the telco
world...over the years, I've spent hundreds of hours tracking down problems
rejected by Bell and AT&T as "not theirs"; at some point, you bump up
against a tech not in denial and the problem gets solved in one heartbeat.
In spite of the turmoil caused by deregulation, competition and advancing
technology have been beneficial.

One thing: you didn't identify the test device correctly.  Just prefix "shi"
to the name and you've got it right.

-rf