I am using Windows 2003 server and it is a Domain controler. I was running great and was also getting accessed from other DC and clients. But after installing Mcafee Enterprise 8i and restarted, the server was disconnected from the network and was not able to access from other DC or clients.
when i ping the gateway, it shows "Destination host un reachable"
Please help me, the server is on halt, and there is a bulk of data to share with users inside.
Bookmark/Search this post with:
not a big deal, most of the times it will be a winsock problem or reinstalling TCP/IP will resolve this problem.
How to remove and reinstall TCP/IP on a Windows Server 2003 domain controller
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.
now here is the way of 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.
Additionally, if you are running Microsoft Windows Server 2003 Service Pack 1, I 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/prodte ... rview.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, I 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.
Even if Winsock is coming back to its position after u restart the server, then you have to 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. I cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
1. Restart the domain controller.
2. When the BIOS information appears, press F8.
3. Select Directory Services Restore Mode, and then press ENTER.
4. Use the Directory Services Restore Mode password to log on.
5. Click Start, and then click Run.
6. In the Open box, type regedit, and then click OK.
7. Locate the following registry subkeys:
HKEY_LOCAL_MACHINESystemCurrentControlSetServicesWinsock
HKEY_LOCAL_MACHINESystemCurrentControlSetServicesWinsock2
8. Right-click each key, and then click Delete.
9. Click Yes to confirm the deletion of each key.
10. Close Regedit.
11. Locate the Nettcpip.inf file in %winroot%inf, and then open the file in Notepad.
12. Locate the [MS_TCPIP.PrimaryInstall] section.
13. Edit the Characteristics = 0xa0 entry and replace 0xa0 with 0x80.
14. Save the file, and then exit Notepad.
15. In Control Panel, double-click Network Connections, right-click Local Area Connection, and then select Properties.
16. On the General tab, click Install, select Protocol, and then click Add.
17. In the Select Network Protocols window, click Have Disk.
18. In the Copy manufacturer's files from: text box, type c:windowsinf, and then click OK.
19. 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.
20. Select Internet Protocol (TCP/IP), click Uninstall, and then click Yes.
21. Restart your computer, and then select Directory Services Restore Mode as mentioned in steps 2 - 4.
22. In Control Panel, double-click Network Connections, right-click Local Area Connection, and then select Properties.
23. On the General tab, click Install, select Protocol, and then click Add.
24. In the Select Network Protocols window, click Have Disk.
25. In the Copy Manufacturer's files from text box, type c:windowsinf, and then click OK.
26. Select Internet Protocol (TCP/IP), and then click OK.
27. Restart your computer.
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 DriveLetter:SupportToolssuptools.msi, where DriveLetter 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 FilesSupport 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.
Get back to me for further issue