Hello folks @ 3000-l,

Re: QCTerm And Disconnects

>> d says:
>>
>>Having said all of this.. Don't change your TCP timers today...  if your
>>network is running fine and these timers really only come into play
>>when you are having a network problem.

Good point...  as long as you have a fast and error free network connection
with sufficient bandwidth which does not experience line drops between the
local and remote host, these TCP timers will not come into play.  The TCP
timers will come into play when an outage of the network link or failure of
a remote host are experienced.

When experiencing a situation where network connections are dropped, I like
to first set the timers to the default and then upon the next outage read
the NMLG files to determine what the failure condition is.

I frequently find that the TCP timers are set to absurd values in an
attempt to address (workaround) network link outages and that little effort
is put into actually addressing the root cause of the problem which is
ongoing network link quality problems.  Setting the TCP timers to large
numbers with many retransmissions can hide infrequent to frequent link
outages, but keep in mind an end user will experience these link outages
as a very very poor performing remote host.

I hope this helps.

Regards,

James Hofmeister
Hewlett Packard
Worldwide Technology Network Expert Center
P.S. My Ideals are my own, not necessarily my employers.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *