Cannot Connect to Server Using Automatic Dialing Feature

• Microsoft Windows NT Server version 4.0
• Microsoft Windows NT Workstation version 4.0

SYMPTOMS

When you connect to a Remote Access Service (RAS) server from a Windows NT RAS client using the automatic dialing feature to access a remote network resource, there may be a long pause of approximately two minutes while the dial-up connection is being established. During that time, the connection dialog box displays the following message:

   Registering your computer on the network...

   \\<servername>, the network path was not found.

CAUSE

RAS is timing out before an IP address can be obtained or confirmed.

RESOLUTION

To resolve this issue, use any of the following methods:

Method 1

After you recieve the error message, you are still connected to the RAS server. Cancel the first attempt, and then try to access the network resource again.

Method 2

Use a protocol other than TCP/IP for your dial-up connection (such as the NetBEUI or IPX/SPX-compatible protocol). You can enable the NetBEUI or IPX/SPX-compatible protocol and disable TCP/IP in the phone book entry properties in Dial-Up Networking (DUN). Note that these protocols must be installed for RAS and DUN to use them. You can install these protocols using the Network tool in Control Panel.

Normally, Windows NT RAS servers act as NetBIOS gateways for the network to which they are attached. Therefore, a RAS client dialing in with only, for example, the NetBEUI protocol can see all Windows NT resources running TCP/IP (assuming the RAS server is configured to use both protocols).

For additional information about the NetBIOS gateway feature of the Windows NT RAS server, see the following Internet web site:

   http://premium.microsoft.com/msdn/library/winresource/dnwinnt/
      f1d/d1f/s7d54.htm

Method 3

Do not use the automatic dialing feature. Connect to the remote network using RAS (using the DUN phone book entry) before trying to access the remote server.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Windows NT version 4.0. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.