Network Protocol Settings on Win16 Clients

The default behavior of Win16 clients is to ignore the site-wide settings for the Default Protocol and LANA number and use NetBIOS instead. This is due to the various versions of the TCP/IP stack that are available for 16-bit clients, some of which are not compatible with the SMS 2.0 listening agent. Win16 clients fall back to the NetBIOS protocol as a safety feature. Therefore, Win16 clients will ignore site settings for protocol unless forced by the Client Options Configuration (Rccliopt) utility.

For sites where the TCP/IP stack is, in fact, compatible with SMS 2.0, the site administrator might wish to change the client-side settings for the Default Protocol and LANA number as they appear in the SMSrc16.ini. Directly editing the values in the SMSrc16.ini file does not accomplish this, because the values can be overwritten by logon scripts, munger activity, and periodic updates from the primary site server.

There are two ways to permanently alter these settings so that the changes will not be overwritten. The first is to use the Rccliopt helper utility, which is described later in this chapter. The second is to make the necessary edits and set a ‘do not overwrite’ flag (UpdateEnabled) in the SMSrc16.ini file.

The procedure for making permanent changes in SMSrc16.ini is as follows:

  1. Create an entry in the [Client Components — Remote Control] section in the SMSrc16.ini file called UpdateEnabled=NO. This prevents updates to the SMSrc16.ini file caused by the mungers periodically overwriting this file and its settings.
  2. Change your Default Protocol to the appropriate protocol:
    • TCP = TCP/IP
    • IPX = IPX
    • IP = UDP (This is the SMS 1.2 default protocol.)
    • NetBIOS = NetBIOS (Be sure to update the LANANum = X entry to the appropriate LANA number at the same time.)
  3. Stop and restart the Wuser agent. You can stop the program and restart it or restart Windows.


Tip   Microsoft’s implementation of the IPX stack is not compatible with SMS 2.0 on Win16 clients. Use the Novell IPX/SPX stack instead of the Microsoft IPX stack when you use Remote Control on Win16 clients.