XP Problem

Philippines
February 20, 2007 3:22am CST
I have an XP machine that ran Microsoft update and now does not see the network. The PC had already loaded the SP2 months prior and was working fine. I can do a local ping, ping other things on the network, ipconfig /all and everything appears to be working correctly. I ran ipconfig /flushdns and it cleared the cache. Tried to re-register or renew and it can not see anything on the network. I tried to restore from a few days back and it restored correctly but did not restore the connection. As I stated earlier....this was working fine until the XP update. The firewall and all the protection has been disabled and still the results. Look at MSinfo and this matches the same as another working machine I am stumped ...looking for some possible tests or corrections.
1 person likes this
4 responses
• Singapore
27 Feb 07
If you have not already disabled the Windows restore service, do a roll-back to before you installed the patch. It may just solve the problem. :)
• India
20 Feb 07
It was the latest bug of the WIN XP2 , just reinstall the OS your problem will be solved, it sometimes happen the drivers of LAN are not properly configured at the time of installation of WIN XP, so if you reinstall it then you can connect to internet or a local LAN once again.I have already seen this problem on few systems and break my head to solve it by all the ways, but none of them worked then i reinstalled the winxp OS thats it it got solved and applied this to all pcs with similar problem, so you too do this it wil lbe solved, there is no other way to solve this.
@ashumit02 (818)
• United States
20 Feb 07
Xp SP2 is the self sufficient to manage its all defects .I think if anybody is using original window xp then he can easily get help from microsoft .Otherwise simply install the new XP operating system to tweak all defects .Firewall must be on for safe network access .
• India
20 Feb 07
You have run all the tests, but you did not mention anything about TCPIP settings. Did you check them or the subnet mask. I guess is that is where the problem could be.