Win95/98/NT Dialup, Authentication, Browsing Using TCPIP, IPX/SPX, or NetBEUI

ID: Q232511


The information in this article applies to:


SUMMARY

Win95/98/NT Dialup, Authentication, Browsing Using TCPIP, IPX/SPX, or NetBEUI

This article has been written to help clarify how Windows NT clients, such as Windows 95, Windows 98, and Windows NT Workstation/Windows NT Server are supposed to be configured in order to successfully dial into a Windows NT network. The functionality of the clients includes dial-up authentication, domain authentication, gaining access to resources, and browsing.

This article can also be viewed as a Microsoft PowerPoint presentation and Webcast at the following location:
http://support.microsoft.com/support/webcasts/past_webcasts.asp
After you connect to the location above, find the presentation titled:

  Support WebCast: Win95/98/NT Dialup and Authentication using
  TCP/IP, IPX/SPX, and NetBEUI 
  Thursday, June 3, 1999: 10:00 A.M. 
  Pacific time (Greenwich mean time - 7 Hours) 
This article is a text summary of the presentation and has been broken down into the following sections:

Review of Networking Objectives

The most common goal for dial-up networking is to be able to provide the following: It is possible that one or more of these steps work, while others do not. To successfully achieve all of the above, look at both the client configuration and the server configuration. But first, a review of the components involved in Dial-up Networking (DUN).

Review of Dial-up Components

The following diagram displays the different DUN components and how they are generally attached to a network.

            M                   M
            O                   O               L
  Dialup ---D--- Phone lines ---D--- Dialup ----A---- Internal network
  Client    E                   E    Server     N       
(95/98/NT)  M                   M  (RAS/RRAS)                  

Software and Hardware Checklist

The following should be verified to make sure you have hardware that is supported and the latest software updates, depending on the client that you are using to dial in with.

Configuration of Clients and Servers (General)


It is important to make sure that each client that dials into a RAS/RRAS server is properly configured. It is also important that the RAS/RRAS servers are properly configured. The following general configurations are recommended for the DUN client, as well as the RAS/RRAS server. These recommendations are not protocol specific and would apply regardless of the protocol being used for DUN. The next few sections deal exclusively with the general configuration of these components.

You may notice in looking at the configurations for each client that there is a great deal of overlap. This is intentional to show that the client operating systems are configured in much the same way as each other. The overlap could have been taken out, but has been left in so that a checklist could be taken straight from this article for each client during troubleshooting or installation.

Windows 95 Configuration (General)

Windows 98 Configuration (General)

Windows NT Configuration (General)

Initial Setup Process

RAS Server Configuration (General)

Please verify the following services and devices are configured on the RAS server:

RRAS Server Configuration (General)

Configuration of Clients and Servers (Protocol Specific)

The following is a breakdown of each client and server configuration based on each of the protocols supported with the Microsoft Windows operating systems: NetBEUI, NWLink, and TCP/IP.

IMPORTANT NOTE: This portion of the reference should only be consulted after the general configuration options above have been verified and are configured correctly. Attempting to come directly to this section could lead to confusion, as the general steps of the configuration are assumed at this point.

The order of how each protocol will be presented is shown in the list below:



Configuration of Clients (NetBEUI)

Windows 95 Configuration (NetBEUI)

Windows 98 Configuration (NetBEUI)

Windows NT Configuration (NetBEUI)

Configuration of Servers (NetBEUI)

RAS Server Configuration (NetBEUI)


RRAS Server Configuration (NetBEUI)

Configuration of Clients (NWLink)

Windows 95 Configuration (NWLink)

Windows 98 Configuration (NWLink)

Windows NT Configuration (NWLink)


Configuration of Servers (NWLink)

RAS Server Configuration (NWLink)


RRAS Server Configuration (NWLink)

Configuration of Clients (TCP/IP)

Windows 95 Configuration (TCP/IP)

Windows 98 Configuration (TCP/IP)

Windows NT Configuration (TCP/IP)


Configuration of Servers (TCP/IP)

RAS Server Configuration (TCP/IP)

RRAS Server Configuration (TCP/IP)

NetBIOS Name Resolution (TCP/IP)

All Clients - Windows 95/98 and Windows NT

When you are using WINS on a network: If not you are using WINS in your network, use an lmhosts file with the following entries (xxx.xxx.xxx.xxx represents the IP address of your PDC):

	xxx.xxx.xxx.xxx  WINPDC   #PRE  #DOM:DOMAIN-TEST
	xxx.xxx.xxx.xxx  “DOMAIN-TEST….\0x1B”  #PRE 

Common Error Messages


REFERENCES

Q236963 How to Create Hardware Profiles in Win95/98/NT 4.0
Q191494 Dial-Up Networking 1.3 Upgrade Available
Q189771 Windows 98 Dial-Up Networking Security Upgrade Release Notes
Q178729 How To Configure Windows 95 to Dial into a RAS/RRAS Server
Q141600 How to Manually Create Hardware Profiles for Laptop Computers
Q150800 Domain Browsing with TCP/IP and LMHOSTS Files
Q183368 Requirements to Browse Network with Dial-Up Networking
Q193836 NET USE Attempt Across Domains Fails Without Name Resolution
Q185786 Recommended Practices for WINS
Q198518 RRAS Requires Non-Zero Internal Network Number for IPX
Q163949 Workstation Using Lmhosts Fails to Logon if DC Unavailable
Q150053 Erratic Domain Logon from Windows 95 Dial-Up Networking

Additional query words:


Keywords          : 
Version           : WINDOWS:95; winnt:4.0
Platform          : WINDOWS winnt 
Issue type        : kbinfo 

Last Reviewed: August 12, 1999