I deleted bojour.exe and tried cleaning up registry. I think I somehow corrupted tcp ip driver in that process. I installed sp3 thinking that it will fix the tcp ip issue. But it didn't work. I unistalled/reinstalled network card drivers. Tried repairing the LAN connections, but it didn't help. I even tried running windows recovery, but instead of showing me Repair OS option, it simply re-installed OS in a duplicate folder. Any way to fix the corrupt tcp ip installation? The LAN connections doesn't dynamically get IP and DNS addresses. If I boot on the new installation of OS on the same computer, the network works fine. Thanks in advance2 people got this answerI do too

Try running netsh int ip reset c:\resetlog.txt. See if this helps: http://support.microsoft.com/default.aspx/kb/299357?p=1-B- http://www.officeforlawyers.com Author: The Lawyer's Guide to Microsoft Outlook

Ben, Thanks a lot for your answer. I used the information you provided and also looked at the article you have mentioned. I spent lots of time fixing the tcp/ip issue, but so far I am not successful. I did following to fix the issue, but has not helped so far. 1. I reset ip using your command and later using the FixIt patch provided in the article you mentioned and rebooted. That didn't help. 2. I also removed Windows Networking Components and reinstalled it. That didn't help either. I also combined that with ethernet adapter drivers uninstall. That didn't work either. 3. I also tried reinstalling XP SP3 wishing that will fix the issue. I was very much disappointed that it didn't. 4. Now I am getting svchost error that one of the instruction could not read memory at 0x00000010, or so when I reboot the computer. When I login all other programs complained. I am not at my desktop which is corrupted. I was getting DCOM service failure as the first exception in the event log. The error was "pipe is in invalid state". I am at the point of giving up. Thanks for your help. Pramod Patel

I also forgot to mention that when I tried to run netsh I am getting the following error: "Initialization function INITHELPERDLL in IPMONTR.DLL failed to start with error code 11003". I also tried reset winsock using netsh. I used netsh command to reset the winsock. It might have reset the winsock even when I used FixtIt patch. However, it is possible, that I may not have done it systematically as described in the following article: http://support.microsoft.com/kb/811259/ I will follow above steps and let you know. Thanks for your help. Pramod

I think I have a theory what is causing the tcp ip problem. I had CISCO VPN v4.7 installed on my XP installation, which corrupted network connections after auto updating some recent fixes. Here is what I did to determine that. 1. After installing XP SP3, I could not recover my old XP installation, but instead when I tried to recover, the recovery console installed a new installation of XP. I systematically created restore points after every new program installation. I installed all the fixes for XP SP1, then installed SP2 and then SP3 (skipped installing all SP2 fixes). 2. I installed most of the usual programs I had on my previous (BAD) XP installation. Created restore points. 3. I verified network connectivity using IE and Firefox. They were working fine. 4. I installed Cisco VPN v4.7 and Symantec Antivirus. The Symantec Antivirus installation failed because the Live Update failed to download the updated virus signature files. 5. I tried connecting to the network and it failed. Got "Network Diagnostics" page on IE. Tried checking it and it showed HTTP, HTTPS and FTP failure with the mention that firewall might be blocking ports 80, 443 etc. 6. I deleted Symantec Antivirus completely to eliminate that from the equation. That didn't resolve the network issue. 7. I restored the system to the state just before I installed Cisco VPN. 8. I installed Cisco VPN 5.0.03.xxx. Then after the reboot, when I tested the network connectivity, everything was working fine. I could connect using IE and Firefox without any issues. I noticed similar Network problem on my work computer as well and after upgrade of Cisco VPN the problem has gone away. So this makes me think that there is something in the new patches that breaks the network connectivity if you are using the other network based software like VPN. I will continue my test on my BAD XP installation and see if I could resolve the issue by replacing VPN software. I will post the results. Thanks Ben for your help. It lead me to many wonderful forum discussions and technotes on network issues. Pramod

Pramod, This is a reply that I received for help in restoring a corrupt Winsock keys with error code 11003. First, I checked to see if the problem was caused by an Layered Service Provider (LSP) as described in the first point, by using the netsh command in cmd prompt: netsh winsock show catalog. After checking the winsock catalogue to determine that there were no LSP's overididing Basic Service Providers, I ran the Winsock XP Fix, as described in the second point, and this resolved the issue with TCP/IP and Winsock connectivity. If there are LSP in the catalogue, you may wish to run the LSPfix as a first step, followed by the Winsock XP Fix. I hope this will of assistance to you. The entire message and related links are below. Another user, -MainFrame-, has replied to a thread you have subscribed to in the System Repair and Recovery Forum. Thread Title Unable to recover TCP/IP connectivity & corrupt Winsock keys with error code 11003 Started by: nzcleman Reply: Hi there nzcleman,http://www.cexx.org/lspfix.htm Read the instructions on how to use LSPFix carefully here: http://www.bleepingcomputer.com/tutorials/tutorial59.html Download and run LSPFix from here: Once run, reboot your system. Now download and run WinsockXPFix from here: http://majorgeeks.com/WinSock_XP_Fix_d4372.html Reboot your system again once WinsockXPFix has finished (although it should reboot for you). Hopefully this will help :)

Thanks for your reply. Since I didn't get anywhere with my bad installation, I installed XP again using Recovery Console (had no choice to repair old installation). Then reinstalled all the programs in the new installation and deleted the old XP installation because I started getting error to activate the XP installation and without network working it was difficult. So in a nutshell, now I don't have the BAD installation where I could try your suggestion to fix the winsock and ultimately network issue. Thanks for your time.