Path: utzoo!mnetor!tmsoft!torsqnt!lethe!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!wuarchive!psuvax1!psuvm!ysub!temngt23
From: TEMNGT23@ysub.ysu.edu (Lou Anschuetz)
Newsgroups: comp.sys.ncr
Subject: Re: WIN-TCP / NFS &/or SLIP Available for Tower?
Message-ID: <91061.205038TEMNGT23@ysub.ysu.edu>
Date: 3 Mar 91 01:50:38 GMT
References: <225@mbitow.UUCP>
Organization: Youngstown State University VM system (YSUB)
Lines: 27

This isn't necessarily a direct followup, but our poster program
has temporarily vanished, and this is sort of related.  First, the
related stuff - I have heard that WIN-TCP has an NFS, but that if
you look up SLOW in the dictionary you would find a TWG NFS command
as the definition (over 2 minutes was the low estimate).  In light
of the not to speedy performance of WIN-TCP in general, I have not
pursued this so cannot verify that this is all true (though it has
that ring....)

Second, I am now sending everyone through a terminal server to my
tower since using HPSIO and modems is not real functional.  This
mostly works REAL well, except that at least once a day, WIN-TCP
decideds not to do anything anymore and quietly quits, thereby
allowing no more users to log in.  I am going to call this one in,
but I have NO error messages (WIN-TCP never writes to its syslog
file, and never reports errors - t'is like a c program, it dies
with no report of its death...).  There may well be a certain parameter
I need to tune, but have no idea what.  I do know that there are
usually about 14 users on board when it quits, though it has run
for 4 hours with this many users pounding away, so it is not
consistent.  Any help would be appreciated.  BTW, the terminal
server is fine during this time, but of course you can't do much
with it since it gets its software from the tower.  I never need
to reload or boot it when this happens.  HELP!  (Jeff at CODAR, look
for another strange call on Monday  :-)

As always, thanks in advance!