Unable to Install TCP/IP Protocol and Component After Setup

 Last reviewed: June 13, 1996
Article ID: Q145953
The information in this article applies to:
  • Microsoft Windows NT Server versions 3.5 and 3.51

SYMPTOMS

If you cancel TCP/IP Configuration during Windows NT Setup and you try to install the TCP/IP protocol and related components after Setup, the TCP/IP Internetworking component, Connectivity Utilities, is unavailable (dimmed).

CAUSE

Windows NT Setup adds the Tcpip subkey in the registry even though you canceled the TCP/IP Configuration during Setup.

RESOLUTION

To correct this problem, do the following:

WARNING: Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to reinstall Windows NT to correct them. Microsoft cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk.

  1. Start Registry Editor (REGEDT32.EXE) and locate the following Registry subkey in the HKEY_LOCAL_MACHINE subtree:

    \SYSTEM\CurrentControlSet\Services

  2. Remove the Tcpip key and its subkeys.

  3. Locate the following Registry subkey in the HKEY_LOCAL_MACHINE subtree:

    \SOFTWARE\Microsoft

  4. Remove the Tcpipcu key and its subkeys.

  5. Quit the Registry Editor.

  6. Shut down and restart Windows NT.

KBCategory: kbsetup
KBSubcategory: ntsetup nttcp
Additional reference words: prodnt 3.50 3.51

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.

Last reviewed: June 13, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.