OK network gurus, here's an unusual problem that's I've been working on for 3 days. I have an eMachine running Windows XP Home Edition. This system has been functioning in my current configuration for several years. The current symptoms are that it will connect via my browser (IE7) to the internet after booting and browser works OK for a few minutes, then it will just stop communicating. No error messages are reported, it just fails to receive any information from any webpage. If rebooted, it will reproduce the problem repeatedly.
Configuration: Connected via integrated Intel Pro/100 VE network adapter to Linksys router with cable internet connection via Surfboard modem
(Note: several other computers in household share same router and work fine)
Background: Problem originated after uninstalling CA Internet Security Suite, uninstall was messy as it did not uninstall cleanly and had to be removed with 3rd party tools. This originally broke all network connectivity, but I was able to restore the connectivity I currently have by uninstalling and reinstalling the network adapter, then resetting Windows firewall setting to default. I was then able to connect to the internet long enough to use CA's online removal tool that is supposed to remove all traces of the Security Suite and clean up the registry. I also made sure that I have all current Windows Updates, scanned for viruses, malware, and spyware.
Current state: As mentioned previously, I can connect via my browser to websites briefly each time I reboot (about 2-3 minutes) and it works normally, then just stops being able to receive any new website data. Strangely, I use Skype and it's connectivity continues to work. I have run the Network Diagnostics and referenced all related material on Microsoft's website for resolving networking/TCP IP issues. Network Diagnostics and manual ping tests reveal the following:
loopback ping test to 127.0.0.1 succeeds
ping test to local host (192.168.1.100) succeeds
ping test to default gateway (192.168.1.1) fails (timeout)
ping test to remote hosts fails (timeout)
Remedies tried thus far:
Updated network adapter driver with latest version, then rolled it back to previous version once it had no impact
Reset TCP/IP using netsh command
Reset firewall to default settings (Windows firewall is currently off)
Tried different ethernet cable
Manually loaded default gateway and DNS servers into TCP IP properties
Tried all steps outlined in http://support.microsoft.com/kb/314067/
Does anybody have any additional remedies to try?
Thanks.
Configuration: Connected via integrated Intel Pro/100 VE network adapter to Linksys router with cable internet connection via Surfboard modem
(Note: several other computers in household share same router and work fine)
Background: Problem originated after uninstalling CA Internet Security Suite, uninstall was messy as it did not uninstall cleanly and had to be removed with 3rd party tools. This originally broke all network connectivity, but I was able to restore the connectivity I currently have by uninstalling and reinstalling the network adapter, then resetting Windows firewall setting to default. I was then able to connect to the internet long enough to use CA's online removal tool that is supposed to remove all traces of the Security Suite and clean up the registry. I also made sure that I have all current Windows Updates, scanned for viruses, malware, and spyware.
Current state: As mentioned previously, I can connect via my browser to websites briefly each time I reboot (about 2-3 minutes) and it works normally, then just stops being able to receive any new website data. Strangely, I use Skype and it's connectivity continues to work. I have run the Network Diagnostics and referenced all related material on Microsoft's website for resolving networking/TCP IP issues. Network Diagnostics and manual ping tests reveal the following:
loopback ping test to 127.0.0.1 succeeds
ping test to local host (192.168.1.100) succeeds
ping test to default gateway (192.168.1.1) fails (timeout)
ping test to remote hosts fails (timeout)
Remedies tried thus far:
Updated network adapter driver with latest version, then rolled it back to previous version once it had no impact
Reset TCP/IP using netsh command
Reset firewall to default settings (Windows firewall is currently off)
Tried different ethernet cable
Manually loaded default gateway and DNS servers into TCP IP properties
Tried all steps outlined in http://support.microsoft.com/kb/314067/
Does anybody have any additional remedies to try?
Thanks.