Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!stanford.edu!agate!usenet.ins.cwru.edu!ysub!temngt23
From: TEMNGT23@ysub.ysu.edu (Lou Anschuetz)
Newsgroups: comp.sys.ncr
Subject: Finding out if TCP/IP is up
Message-ID: <91130.081040TEMNGT23@ysub.ysu.edu>
Date: 10 May 91 12:10:40 GMT
Organization: Youngstown State University VM system (YSUB)
Lines: 22

I have an NCR Tower 700 with 16MB of memory.  All my users come in
through the Ethernet board via a terminal server.  It is possible
for certain dialup users (Commodore 64 in fact) to reboot their
machines while still on line.  Since this "information" is just
passed down the pipeline to the tower, it attempts to handle this
by allocating thousands of 2k streams.  I am already set at maximum
for 2k streams, so there is nothing further I can do there.  The
problem is that WIN TCP/IP on seeing this error quietly dies.
In fact, WIN TCP/IP *NEVER* generates any errors, so it is
impossible to use any automated system to determine if TCP/IP
is up or not based on any kind of error logging.

What I need, therefore, is a way to determine if TCP/IP is up
from cron.  If it is not I can do a win restart (a little
undocumented feature....).  But, how do I do the test?  If it
is down, netstat NEVER returns so I can't use that as a test.
Any help would be really appreciated (we have been down twice
this week for over 8 hours each time - making my users an
unhappy lot.....).  Thanks in advance!

Lou Anschuetz
temngt23@ysub.ysu.edu