Very Bizarre Internet Connectivity Problem - XP Home, SP2

  • Thread starter Thread starter paparush
  • Start date Start date
P

paparush

Fully patched XP Home, SP2
Verizon DSL through Westell 327W

Wired ethernet between my box and the Westell via the onboard
Broaddcom 440x 10/100 Integrated Controller.

This setup has run flawlessly for 2 years.

As of last night, my Internet connection drops out about 9-10 minutes
after rebooting. That is to say, connections time out when trying to
browse to websites in FF and IE.

However, I can still ping websites and get good return times.

At the same time, my laptop, which uses wireless to connect to the
Internet via the Westell still works fine.

If I reboot my desktop box, I can surf the web flawlessly for 9-10
minutes then ..splat..I get connection timeout, "site is taking too
long to respond" errors. But, I can ping the same site and get TTL =
51. In this state, when I try to browse to a site, I see the light
flashing on my NIC connector ,and I see the corresponding light
flashing on the Westell.

I've tried everything I can think of:
Updated NIC driver.
No other network connections installed.
Reset Westell.
Ran netsh int ip reset
Ran ipconfig /release & /renew
Nothing of interest in the Event Viewer.

Its almost like a buffer is getting full, but what?

Any ideas?

Thanks!
 
paparush said:
Fully patched XP Home, SP2
Verizon DSL through Westell 327W

Wired ethernet between my box and the Westell via the onboard
Broaddcom 440x 10/100 Integrated Controller.

This setup has run flawlessly for 2 years.

As of last night, my Internet connection drops out about 9-10 minutes
after rebooting. That is to say, connections time out when trying to
browse to websites in FF and IE.

However, I can still ping websites and get good return times.

At the same time, my laptop, which uses wireless to connect to the
Internet via the Westell still works fine.

If I reboot my desktop box, I can surf the web flawlessly for 9-10
minutes then.. splat.. I get connection timeout, "site is taking too
long to respond" errors. But, I can ping the same site and get TTL =
51. In this state, when I try to browse to a site, I see the light
flashing on my NIC connector, and I see the corresponding light
flashing on the Westell.

I've tried everything I can think of:
Updated NIC driver.
No other network connections installed.
Reset Westell.
Ran netsh int ip reset
Ran ipconfig /release & /renew
Nothing of interest in the Event Viewer.

It's almost like a buffer is getting full, but what?

Any ideas?

Thanks!
Click to expand...

I would suspect the NIC. But why it would still ping, I don't know.
Also try a network group where such oddities are frequently discussed.
 
Back
Top