Trouble surfing with new cable broadband
CB
Ƹ̵̡Ӝ̵̨̄ƷDer Millionendorf- Icrontian
I just got Cable Broadband about a week ago. Since then, I've been having an issue with the web.
When I click a link, short-cut, or bookmark I get a 404 error on the first try.
It always gets the error the first time I go to a particular server in that session. Once I'm there I can navigate freely within the server, but if I click a link to another server (or try to go to another server in any other way) I'll get the error first. I usually have to reload at least three times to get the new server to show, but sometimes it happens in only one refresh, and it never takes more than six.
This happens in IE, Mozilla, and Opera.
It happens on all of the computers on my network (all XP).
It only effects web. No other internet-based transmissions are effected.
It's only been happening since Friday afternoon, when the Cable broadband modem was installed. Friday morning it was fine.
Here's the weirdest part:
It doesn't happen when I take the router out of the loop and connect my system directly to the cable modem.
Of course, this means that the Time Warner techies wont help me because it's obviously my router, not the modem or connection.
I've never heard of a router interfering with a web connection this way. In fact, if someone asked me weather this problem was possible, I would tell them that it is not, because the router just doesn't work in a way that could effect browsing this way...
The router is a Netgear 4-port/wireless. All of the systems are connected to the router by cable.
The next step in my mental trouble-shooting diagram of this issue is to try a different router. Unfortunately, I've only got the one.
Anybody seen this before?
When I click a link, short-cut, or bookmark I get a 404 error on the first try.
It always gets the error the first time I go to a particular server in that session. Once I'm there I can navigate freely within the server, but if I click a link to another server (or try to go to another server in any other way) I'll get the error first. I usually have to reload at least three times to get the new server to show, but sometimes it happens in only one refresh, and it never takes more than six.
This happens in IE, Mozilla, and Opera.
It happens on all of the computers on my network (all XP).
It only effects web. No other internet-based transmissions are effected.
It's only been happening since Friday afternoon, when the Cable broadband modem was installed. Friday morning it was fine.
Here's the weirdest part:
It doesn't happen when I take the router out of the loop and connect my system directly to the cable modem.
Of course, this means that the Time Warner techies wont help me because it's obviously my router, not the modem or connection.
I've never heard of a router interfering with a web connection this way. In fact, if someone asked me weather this problem was possible, I would tell them that it is not, because the router just doesn't work in a way that could effect browsing this way...
The router is a Netgear 4-port/wireless. All of the systems are connected to the router by cable.
The next step in my mental trouble-shooting diagram of this issue is to try a different router. Unfortunately, I've only got the one.
Anybody seen this before?
0
Comments
Is your router handing out ip addresses or have you statically assigned them? Another question, is if you have onboard network cards and if so, are they autosensing? There have been many problems with dropped packets on some routers due to the autosensing capability of some integrated nics. LMK...kay....
If that doesn't fix your problem, try a different router.
My suggestion is to blow out the router config, reset to factory defaults, update the firmware if there is one available, and reconfigure it from scratch. There could be all kinds of weird issues like a corrupt ARP cache or something like that.
When I talked to him on the phone yesterday that's what he said he was going to do... judging by the fact that he hasn't been online today, it may not have worked!
I only work a half-day on Wednesdays, so when I get home this afternoon, I'll go to Netgear's site, and see if they have a firmwear update for this model.
Turns out that it takes more than just pushing the button to reset the router, you have to hold it in for almost a minute.
I found that out when I got to the end of the instructions for updating the firmware.
It's working perfectly now. I'm not sure if it was the update or the reset, but I guess it doesn't matter.