Table of Contents
Advertisement
Problem
Remote connection requests in the server queue are delayed in being
connected to a printer on an ACCESS DYNAMIC port.
Correction: No printing tasks can execute until a local user discon-
nects his or her sessions and logs out. You can define the port char-
acteristic INACTIVITY LOGOUT as ENABLED. Then if a local
user has no active sessions, the server logs the user out automati-
cally when the INACTIVITY TIMER expires. Assign a value to
INACTIVITY TIMER with the SET SERVER or DEFINE SERVER
command.
Correction:
If
printing requirements justify it, set ACCESS to
REMOTE so that only remote sessions are serviced at the port.
4.5 PROBLEMS INVOLVING SERVICE NODES
Problems can occur which involve the interaction between the MUXserver 100
and one or more service nodes.
If
the same problem appears to involve a num-
ber of service nodes and more than one server, it may be an Ethernet malfunc-
tion (refer to Section 4.6, PROBLEMS INVOLVING THE ETHERNET).
However,
if
the problem occurs during communication with a particular service,
it is likely to be associated with a service node's hardware (including its
Ethernet interface), or the service node LAT software.
A terminal user often becomes aware of service node problems when error mes-
sages appear. The messages tell why a connection cannot be established or why
a service session has been terminated.
4.5.1 Message Timing Problem
An error has occurred involving the timing of messages transmitted between
the MUXserver 100 and a service node. One of the error messages in the fol-
lowing groups may appear:
Local -201- Connection to 'name' not established
No response within timeout period
Local -206- Connection to 'name' terminated
No response within timeout period
36
CHAPTER 4 MUXserver 100 TROUBLESHOOTING
Advertisement
Table of Contents
