RE: TCP/IP Knocked Out...

[Justin Haase <JHaase@xxxxxxxxxxxxx>]

Not sure if this is the same on that old of an OS/machine, but can you do a
WRKHDWRSC *CMN and see if it shows Operational?  Since everyone is off the
box anyway, why not save the troubleshooting and just IPL it, providing TCP
is in the startup job?

I know, it's a Windows answer, but for a quick fix (shoot first, ask
questions later) it should work.

jch

-----Original Message-----
From: Edward Marczak [mailto:erm@rainstormstudios.com]
Sent: Thursday, January 02, 2003 3:29 PM
To: midrange-l@midrange.com
Subject: TCP/IP Knocked Out...


...and I'm not physically in that office right now.  No lights on the
Ethernet card.  Had someone on-site replace the Ethernet cable.  No luck
(although we get a solid link light on the hub - I know that can be a 'false
positive').

Basically, everyone connecting via IP got dumped at the same time.  Users on
Twinax are OK.

I don't have access to the machine (and therefore log files) right now.

Is there a diagnostic I can run on the card?  Anything else that would tell
me what the problem is? (all done by leading someone over the phone!)

This is on an older CISC based machine running R3V2, if that makes any
difference.

Thanks.
--
Ed Marczak

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.