Problem # 1 (20 Sept 1990) Eva Hatcherson

Our intention was to set up 8 ports on a terminal server, UTSV28, to
offer a service called LAN which, when a user connected to it, would
allow the user to use the Local Area Network.  However, we found that
when we initially set up this service, a user would have to issue the
command DISCONNECT SERVICE LAN at the local prompt of the  terminal
server in order to free up that service once they were finished using
the LAN.  It would not automatically disconnect from the service.

Solution # 1

The following characteristics or parameters had to be enabled
on each terminal server port that was to offer the service LAN:

Access:        Remote
Break:         Disabled
Modem Control: Enabled
DSRlogout:     Enabled
DTRwait:       Enabled
Autoprompt:    Disabled
Broadcast:     Disabled

The following parameters had to be enabled on the S-Mux controlled
by Tech Control in K-lab (x8888):

DCD Control : ON
DSR Control : ON


Problem # 2

After we successfully got the service LAN to disconnect automatically,
there were some circumstances where, once the service LAN was 
disconnected, the process on the remote node (VAX) would still be
open, and therefore allow someone to later come in on the same port 
and drop directly into that process.

Solution # 2

The characteristic DTR needed to be enabled on the S-MUX controlled by
K-lab (x8888).  Whenever a user logs out of a terminal server, the
server drops the signal DTR.  That "droppage" is transmitted clear
through to the remote node (VAX), and when the remote node senses
that DTR has been dropped, it stops the process.  Since DTR was not
initially enabled on the S-MUX, the fact that DTR was getting dropped
was not able to pass through the mux to the VAX, and therefore the VAX
left the process connected.

***************************************************************************