Quote:
Originally Posted by JohnWill Well, he is saying that more than one computer has some issues... |
Absolutely; and I'm glad you're pursuing the line quality question.
The "however" is that I agree with the thread title, and am not convinced that the second computer is having anywhere near the same extent of problem.
EDIT: By the way, I spent a lot of time studying the initial post and arguing with myself before posting; I had not seen your post # 2 until after I had posted # 3.
The parts about IM working when browser fails and a reboot fixing the problem for 30 minutes is not inconsistent with a corrupted firewall, driver or stack/winsock.
I leave it up to
subarusti4 whether to pursue the issue from both ends at once. Heck, the problem could be in the "middle"--the router. My suggestions for the PC are three ...
1. Uninstall the non-Windows firewall or security suite.
2. Use Device Manager to uninstall the networking adapter; reboot and let Windows discover the adapter and reinstall the driver.
3. If I have the OS wrong ask for the correct repairs ...
(From a JohnWill post)
TCP/IP stack repair options for use with Windows XP with SP2 or SP3. Start, Run, CMD, OK to open a command prompt.
Reset WINSOCK entries to installation defaults:
netsh winsock reset catalog
Reset TCP/IP stack to installation defaults.
netsh int ip reset reset.log
Reboot the machine.