Troubleshooting Tips

If a prospective 32-bit NetWare bindery client is discovered but not installed:

• Verify that the NetWare Bindery Logon Client Installation method is initiated for the site in the SMS Administrator console.
• Check to see if the Nw_logon.log file is the only log file in the client’s %Windir%\MS\SMS\Logs directory. If it is, there might have been a problem reading files from the NetWare server. Check the log for details.
• Check to see if the site server has completed installation of the NetWare logon point. The NetWare system logon script might be changed, and the user at the prospective client might log on, before the site server has completed the logon point installation. In this case, files required for client software installation might not be available.
• Verify that the prospective client’s IP address or IPX network number is within the IP subnet or IPX network number range specified in Site Boundaries in the SMS Administrator console.

  At the client, examine the Nw_logon.log file to determine which IP subnets or IPX network numbers the client found from its network configuration Verify that the site boundary assignments have been copied from the site control file to the information stored for the site in the Netconf.ncf file in the \\<LogonPoint>\SMSLogon\Sites\<SiteCode>\ directory. You can open the Netconf.ncf file in Microsoft Notepad, but do not attempt to change this file directly.

If a prospective 32-bit NetWare bindery client that logs on to a NetWare 4.x Bindery Emulation server is not installed:

• Verify that the Bindery Emulation server was rebooted with its Bindery Emulation set and that the correct Bindery Emulation is active. If not, the site server cannot update the NetWare logon point and the prospective client will not be able to connect to the logon point.