Ref: 05270022
Title: Sessions across inter-networks that don't terminate
Date: 7/18/88

Copyright 3Com Corporation, 1991.  All rights reserved.

If you frequently initiate sessions with servers on a non-local
network, you may occasionally experience problems.  The errors you may
see are usually "Server not responding," "Transmission failed," or
"Redir error 51."  Below are a few guidelines that may keep these to a
minimum, if everyone follows them:

1.  The number of `remote' sessions a server may maintain is
limited, so you should maintain the session ONLY AS LONG AS YOU
NEED IT.

Remote sessions is determined by the number of Message Buffers
(3Install, 3Share parameter screen) minus One. 3+1.3 has increased
this limit by allowing IDP.SYS to keep track of 100 Remote
Sessions.

2.  Your first link to the remote server creates a session--so
you must unlink EVERYTHING on that server to terminate
your session.

3.  The NETCONNECT server, which passes packets destined for
remote nets, WILL NOT TERMINATE YOUR SESSION TO THE REMOTE
SERVER IF YOU REBOOT BEFORE UNLINKING.  If you link to the
remote server, then reboot, that session is still maintained
by the server.  You must specifically `3F UNLINK' or `LOGOUT' to
terminate that link.

4.  If you are linking to the remote server for tools or anything that
can be maintained on your server make copies available on your
local network. Keep internet traffic to a minimum.

5.  Operations that create a high amount of internetwork traffic
(such as large file transfers) can degrade the performance
for other internet users.  Keep these operations to a minumum,
or do them at non-peak hours.

6.  Turning your PC off doesn't log you out, or terminate
any links.  You should never turn your workstation off
unless you LOGOUT first.
