Microsoft KB Archive/325356

= How to remove and reinstall TCP/IP on a Windows Server 2003 domain controller =

Article ID: 325356

Article Last Modified on 11/1/2006

-

APPLIES TO


 * Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
 * Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)
 * Microsoft Windows Server 2003, Web Edition
 * Microsoft Windows Server 2003, 64-Bit Datacenter Edition
 * Microsoft Windows Server 2003, Enterprise x64 Edition

-



This article was previously published under Q325356





For a Microsoft Windows 2000 version of this article, see 299451.

Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry



SUMMARY
This article describes how to remove and then reinstall TCP/IP and Winsock on a Windows Server 2003-based domain controller.

When you troubleshoot an issue, you may suspect that a TCP/IP or a Winsock related component is either corrupted or damaged. Therefore, you may try to remove TCP/IP and all related components, including registry entries. However, you may discover that you cannot finish this operation. The following procedure describes how to remove and then reinstall TCP/IP on a Windows Server 2003-based domain controller.

Important notes  We recommend that you follow the steps in Microsoft Knowledge Base article 317518 if you have to reset TCP/IP on a Windows Server 2003-based domain controller. The article discusses the preferred method of restoring the TCP/IP stack to its original state.

For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:

317518 How to reset &quot;Internet Protocol (TCP/IP) &quot; in Windows Server 2003

Additionally, if you are running Microsoft Windows Server 2003 Service Pack 1, we recommend that you repair Winsock by using the netsh winsock reset command. For more information about the netsh winsock reset command, visit the following Microsoft Web site:

http://www.microsoft.com/technet/prodtechnol/windowsserver2003/servicepack/overview.mspx

Warning Programs that access or monitor the Internet such as antivirus programs, firewall programs, and proxy clients may be negatively affected when you run the netsh winsock reset command. If you have a program that no longer functions correctly after you use this resolution, reinstall the program to restore functionality. Use the following procedure only when all other troubleshooting procedures have been unsuccessful in resolving the issue. Before you perform this procedure, Microsoft strongly recommends that you back up your computer.

Warning Microsoft recommends that you read this whole procedure before you start to make sure that you have a clear understanding of the procedure.



SYMPTOMS
You may experience one or all of the following symptoms:  An error occurred while renewing interface 'Internet': An operation was attempted on something that is not a socket. When you issue the ipconfig /renew command, you may receive the following error message: “An error occurred while renewing interface local area connection: an operation was attempted on something that is not a socket. Unable to contact driver Error code 2”</li> In the Device Manager, when you click Show Hidden Devices, TCP/IP Protocol Driver is listed as disabled under &quot;Non-Plug and Play drivers&quot;, with error code 24.</li> When you create a dial-up connection, you may receive the following error message: Error 720: No PPP Control Protocols Configured</li> When you issue an ipconfig command at a command prompt, you may receive an error message that is similar to one of the following:

The operation failed since no adapter is in the state permissible for this operation

The attempted operation is not supported for the type of object referenced.

</li> When you issue the Netsh int ip reset resetlog.txt command at a command prompt, you may receive the following error message:

Initialization function INITHELPERDLL in IPMONTR.DLL failed to start with error code 10107.

</li></ul>

When you use the ping command, the output displays characters that replace the IP address. For example, output may be similar to the following:

Ping statistics for:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), C:\>ping www.contoso.com

Pinging www.contoso.com [?] with 32 bytes of data:

Reply from 131.94.57.182: bytes=32 time=86ms TTL=236

Reply from 131.94.57.182: bytes=32 time=74ms TTL=236

Reply from 131.94.57.182: bytes=32 time=74ms TTL=236

Reply from 131.94.57.182: bytes=32 time=74ms TTL=236

Ping statistics for Où?: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds: Minimum = 74ms, Maximum = 86ms, Average = 77ms OR

C:\>ping 131.94.57.182

Pinging ? with 32 bytes of data:

Reply from 131.94.57.182: bytes=32 time=73ms TTL=236

Reply from 131.94.57.182: bytes=32 time=74ms TTL=236

Reply from 131.94.57.182: bytes=32 time=73ms TTL=236

Reply from 131.94.57.182: bytes=32 time=73ms TTL=236

Ping statistics for Où?:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds: Minimum = 73ms, Maximum = 74ms, Average = 73ms

<div class="resolution_section">

RESOLUTION
To resolve this issue, delete the corrupted registry keys, and then reinstall the TCP/IP protocol.

To delete the corrupted registry keys, follow these steps.

Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk. <ol> Restart the domain controller.</li> When the BIOS information appears, press F8.</li> Select Directory Services Restore Mode, and then press ENTER.</li> Use the Directory Services Restore Mode password to log on.</li> Click Start, and then click Run.</li> In the Open box, type regedit, and then click OK.</li> Locate the following registry subkeys:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock2

</li> Right-click each key, and then click Delete.</li> Click Yes to confirm the deletion of each key.</li> Close Regedit.</li> Locate the Nettcpip.inf file in %winroot%\inf, and then open the file in Notepad.</li> <li>Locate the [MS_TCPIP.PrimaryInstall] section.</li> <li>Edit the Characteristics = 0xa0 entry and replace 0xa0 with 0x80.</li> <li>Save the file, and then exit Notepad.</li> <li>In Control Panel, double-click Network Connections, right-click Local Area Connection, and then select Properties.</li> <li>On the General tab, click Install, select Protocol, and then click Add.</li> <li>In the Select Network Protocols window, click Have Disk.</li> <li>In the Copy manufacturer's files from: text box, type c:\windows\inf, and then click OK.</li> <li>Select Internet Protocol (TCP/IP), and then click OK.

Note This step will return you to the Local Area Connection Properties screen, but now the Uninstall button is available.</li> <li>Select Internet Protocol (TCP/IP), click Uninstall, and then click Yes.</li> <li>Restart your computer, and then select Directory Services Restore Mode as mentioned in steps 2 - 4.</li> <li>In Control Panel, double-click Network Connections, right-click Local Area Connection, and then select Properties.</li> <li>On the General tab, click Install, select Protocol, and then click Add.</li> <li>In the Select Network Protocols window, click Have Disk.</li> <li>In the Copy Manufacturer's files from text box, type c:\windows\inf, and then click OK.</li> <li>Select Internet Protocol (TCP/IP), and then click OK.</li> <li>Restart your computer.</li></ol>

After you reinstall TCP/IP, install Microsoft Windows Support Tools, and then run the Netdiag and Dcdiag tools to verify that the domain controller is functioning correctly. To do this, follow these steps:
 * 1) Insert your Windows Server 2003 CD-ROM in your computer's CD-ROM or DVD-ROM drive.
 * 2) Click Start, click Run, type  :\Support\Tools\suptools.msi, where   is your CD-ROM or DVD-ROM drive, and then click OK.
 * 3) Follow the instructions on the screen to complete the installation of Windows Support Tools.
 * 4) At the command prompt, locate the folder where the Support Tools were installed. By default, this folder is C:\Program Files\Support Tools.
 * 5) Type dcdiag /v for domain controller diagnostics, and then address any errors.
 * 6) Type netdiag /v for network diagnostics, and then address any errors.

<div class="references_section">