Managing SNAplus2 Clients
Managing Win32 Clients
server has been contacted, the client then tries using directed messages to one or more named servers (specified by the following lines of the file).
•In situations where the client cannot reach any servers using UDP broadcasts, and must use directed messages, specify the name of the first server it should try to contact. This applies in the following cases:
•When the SNAplus2 LAN spans multiple TCP/IP subnets, and there are no SNAplus2 servers in any TCP/IP subnet that the client can access using UDP
•When UDP support is not installed on the client.
•In other cases, the use of UDP broadcasts is optional; to specify that broadcasts should not be attempted, specify the name of the first server instead of *.
The Registry data type of this value is REG_SZ. Specify the names of additional SNAplus2 servers that the client should contact, in order of preference. If the client has tried to contact a server using a UDP broadcast (or has tried to contact the server specified in Server1), but has received no response, it then attempts to contact the server specified in Server2 using a directed message. If this fails, it tries the server specified in Server3, and so on.
These server names are optional, but provide a backup mechanism if the broadcast method of locating a server fails or if the server specified by Server1 is unavailable.
If the client tries all the servers listed without success, it waits for the number of seconds specified by the server_lost_timeout parameter, then restarts the process of trying to contact a server (either with UDP broadcasts or with the first server listed).
262 | Chapter 11 |