TCP/IP Fails to Bind to Server After You Install RAS Server

Article ID: Q132157
Creation Date: 29-JUN-1995
Revision Date: 24-SEP-1996

The information in this article applies to:

Microsoft Windows NT Workstation versions 3.5 and 3.51

Microsoft Windows NT Server versions 3.5 and 3.51

Microsoft Windows NT Server version 4.0

Microsoft Windows NT Workstation version 4.0

SYMPTOMS

After you install the Windows NT Remote Access Service (RAS) server with TCP/IP enabled for dial-in or a RAS client with dial-out TCP/IP support, and restart Windows NT, the following error message appears:

   At least one service or driver failed during system startup

The following events appear in the system log:

   Event ID: 2504
   Source: Server
   Type: Error
   Description: The server could not bind to the transport
                \device\Netbt_Nicdrvr.

   Event ID: 2144
   Source: Workstation
   Type: Error
   Description: The computer name already exists on the network.

CAUSE

This error occurs when a Windows Internet Naming Service (WINS) server uses static mappings for the RAS computer name. The computer was initially mapped as a unique name type. However, when the computer uses RAS, it becomes multihomed. Because of the static mapping, when the computer tries to register as multihomed, it is denied and a duplicate name is reported.

RESOLUTION

To correct this problem, do one of the following:

Delete the static mapping. After the mappings are deleted, reboot the RAS server. It will register itself correctly with the WINS server.
-or-

- If you prefer to use static mappings, delete the unique mapping for

   the computer and re-map the entry as multihomed, entering the IP
   address for the network interface card (NIC) only. Do not enter the IP
   address for the RAS server.

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.