Login Problems
This section discusses various symptoms of common problems related to the login process and the potential solutions. If, after connecting, users are unable to access any network resources, use the following list of troubleshooting guidelines to isolate the problem:
- In the NET.CFG file, verify the following for a Windows 3.x workstation:
SPX Connection = 60For NetWare 4.x (or later): Preferred Tree = <tree name>For NetWare 4.x (or later): NetWare Protocol = NDS, Bind
The NetWare Protocol statement might also specify one protocol if the server environment is homogenous (all NetWare servers of the same version).
- In the CONFIG.SYS file, verify the following:
Files = 75 (minimum)Buffers = 40 (minimum)
- Install the latest Novell ClientTM software or Virtual Loadable ModuleTM (VLMTM) client software on the workstation before you install the dialers.
- In the NIASCFG utility on the server, verify the following:
- Any specified Home Server is running IPXRTR.NLM.
- Any user-specified IPX address is not duplicated in the network. To verify duplication, remove the address from the user's configuration. If the user can access the network, the IPX address must be a duplicate. Make sure that all user-specified IPX addresses are unique.
- PPPRNS IPX network address is unique.
- On the file server, perform the following:
- Set Reply to Get Nearest Server to ON.
- Apply all current OS, CLIB, LAN, and Sequenced Packet ExchangeTM (SPXTM) patches.
- Apply all current Novell Directory ServicesTM (NDSTM) patches for NetWare.
- Set Maximum Packet Receive Buffers to 2000.
- Set Minimum Packet Receive Buffers to 500.
If the user is unable to establish a PPP connection at all, use the following list of troubleshooting tips to help isolate the problem:
- In the NIASCFG utility, verify that security for NWCAP is enabled. If the user is using the Novell Mobile Dialer, verify that CHAP or PAP is enabled. If the user is using Windows 95 dial-up networking, verify that the user has a remote client password configured.
- Connect the modem on a COM port to bypass the communications adapter.
- Set the data rate to 19,200 when you use AIOCOMX.
- Apply the current driver for the communications adapter.
- For NetWare 4.x or later, make sure that the Connect Rights Level is set correctly to allow the user to be authenticated by this server.
The Container context (Connect Rights Level) is defined when you create the CONNECT object in the NDS tree during Novell Internet Access Server 4.1 installation. All users in the Connect container and below can access remote access, except those users in containers that are blocked with the Inheritance Rights Filter. A user not belonging to the Container context might fail to establish a connection.
Use NIASCFG (parameter path: Select Configure NIAS > Remote Access > Generate Configuration Report > Screen) to determine whether Connect Rights are set correctly.
Use NWADMIN to verify or grant additional rights of the CONNECT object for the server. The CONNECT object requires Browse rights to all properties of the user object to authenticate the user.
- Decrease the DCE-to-DTE data rate to 57,600. Use the modem script editor, WMDMMGR.EXE (in SYS:SYSTEM\UTILS), to change this value for the modem.
| |
|
|