Dial up Networking connects but can't log in

  • 2910133
  • 11-Jul-1996
  • 08-Mar-1999
  • 17

Archived Content: This information is no longer maintained and is provided 'as is' for your convenience.


PLEASE NOTE: This TID covers specific issues for logging in via PPPRNS to a NWC or NIAS 4.1 server AFTER YOU ARE CONNECTED. If you are having problems getting connected please refer to "NWC, NIAS 4.1 and Windows 95 PPPRNS Tips"
for more general configuration and troubleshooting tips.

After the NetWare Connect server has been patched to version 2.0.28 or later, Windows 95 remote clients can dial in with Dial-Up Networking (DUN) using PPP. After the dial-up connection is established, the login box for the client you have installed (i.e. Client 32, intraNetWare Client, or the Microsoft Client for NetWare Networks) should pop up automatically after making the connection and you should be able to log in to the network. You should also be able to browse network resources in Network Neighborhood. If you cannot, proceed through the following troubleshooting steps:

1. Load NWCCON. Choose Set Up NetWare Connect. Choose Select NetWare Connect Services. Highlight PPPRNS (it should be set to Yes) and enter. Make sure that the IPX number for the PPPRNS service is unique and is not being used by the server or any other device on the network. If it is not unique, or you are not sure, change the number to a unique number and then exit out making sure to save the changes and restart the service when prompted. You should then be able to type DISPLAY NETWORKS at the console prompt and see the number listed as a valid network. If the new number does not appear in the list of known networks, unload NWCCON, run NWCSTOP, unload IPXRTR, and then run NWCSTART. The new number will now appear in the DISPLAY NETWORKS listing.

2. From the NWCCON main menu, choose Configure NetWare Connect. Choose Services. Choose PPPRNS. Choose Set IPX Parameters, and then walk the tree and check ALL users and any single dot "." (which represents the container) and remove all entries from the Home Server list. Make sure ALL home server lists are empty.

3. Make sure that the NWCSTART.NCF file has been edited to include a "LOAD IPXNLP" statement. This needs to be done when installing the NWC206, NWC207, and NWC208 patches. The IPXNLP.NLM is loaded immediately after the IPXRTR.NLM. This is documented in NWC206.TXT.
***NOTE: If you are running IPXRTR.NLM version 6.50 (May 15, 1997) or later, IPXNLP is no longer necessary and should not be loaded. You will get public symbol errors when loading IPXNLP if you have IPXRTR 6.50 or later. In this case, remove the LOAD IPXNLP line from the NWCSTART.NCF file.

4. Make sure that Reply to Get Nearest Server is set to ON. To check this parameter, load SERVMAN, choose Server Parameters, and then choose Communications.

1. Verify in the network properties that the IPX/SPX-compatible protocol is bound to the Dial-Up Adapter. In addition, if you are using the Client 32, the IPX 32-bit protocol for Novell NetWare Client 32 should also be bound to the Dial-Up Adapter. See "NWC, NIAS 4.1 and Windows 95 PPPRNS Tips" for a list of required network components based on your configuration.

2. If you are using the Novell Client 32 or the intraNetWare Client on your dial-in workstation, verify the following in the properties of the client:
--For 4.x or later networks, "Log in to tree" should be checked and a preferred tree should be set.
--For 3.x networks or mixed environments where you will be accessing only 3.x servers, "Log in to server" and "Bindery connection" should be checked and a preferred server should be set.

3. Verify in the server type properties of your Dial-Up Networking connection that "Log on to network" is checked. Also, verify that you have specified the correct Primary Network Logon in your network properties.

4. Remove the Dial-Up Adapter and reinstall the Dial-Up Adapter. You may also have to remove the NW Client, reinstall the Dial-up Adapter and reinstall the NW Client. See "Instructions for Dial-Up Adapter installation".

Feedback service temporarily unavailable. For content questions or problems, please contact Support.