Dropping internet connection.
bothered
Manchester UK
I needed to update the firmware on my Linksys BEFSR41 router, simple enough. That was on Wednesday. It was for a problem on a couple of CoD servers that was solved as soon as I did the update. Soon after this I started dropping my internet connection, 2\3 times a day. I blamed NTL for this as its happened before with them. Rebooting the NTL box didn't always reconnect me. If I just reset the router the connection comes back, everytime!
It looks like it's the router and not NTL, I only realised this last night and I have to go to work shortly. Could anybody give me some things to check when I get home?
Cheers guys.
It looks like it's the router and not NTL, I only realised this last night and I have to go to work shortly. Could anybody give me some things to check when I get home?
Cheers guys.
0
Comments
Just take screens of most every page. Tedious, I know, but it could really help.
Thrax, which pages would you like to see? It seems to have all been reset to defaults, even the few ports I had forwarded for a few games have now closed.
I'll try the fix they recommended.
How do you have the rest of these set?
He did seem to think that would solve it and it has stayed on since so it looks promising. If we both have the same problem with the same router after updating the firmware maybe they have had a few enquires about it? We'll have to see how it goes. I'll update this thread tomorrow with how things have gone.
Same here.
Off to work now, I'll see when I get in.
It's looking good. I've not lost a connection since the tech support. The number I phoned was on Linksys UKs site. I thought the guy had an 'unusual' accent, at the end he said "are you in the UK?" "yes, arn't you?" replied bothered. "No, I'm in Irving" I wondered who Irving was and whether I should ask, "It's in California" he said. Phew!
Thank you California Linksys man.
Blimey.
I upped the client lease time to see if that makes a difference.
Has it improved at all or is it as bad as ever?
the difference is that mine is an access point.
So ...we'll see.
Windows stock uses MTU of 1492 in size for ethernet-- and remember, with a router in place as a Gateway, your Windows clients think they ARE on an ethernet as far as technical behavior in lower level networking. That fix synced router's MTU to your Windows box(es)' default settings, most probably.
Mismatch of that between router and client box(es) nic(s) will cause a sync mess as far as data flow between client box(es) and router on LAN side. BTW, you might have been talking to someone who is in reality a Cisco-trained support person. Cisco owns Linksys now, and one of the things they worked on was tech support quality. They have a support center in Irvine, CA-- and that might sound like Irving to someone across the pond from me (e is silent).
Suggested mnemonic relation to remember stock MTU value for Windows from 95 OSR 2.1 up-- It's exactly same as year Christopher Columbus "rediscovered" America. That WAS deliberate as well as being a size boundary that could be used with cheap Novell compatible NICs also.
HTH to explain what happened and why fix worked.
http://www.wired.com/news/technology/0,1282,63705,00.html?tw=wn_tophead_1
There's an article on Wired News this morning talking about problems with the way Windows XP handles WiFi connections - stopping and starting the Wireless Zero Configuration tool should fix it. I haven't come across it, but my gf's parents are having problems with theirs and the next time I'm in NYC, I'll need to investigate.
As fra sa im"porvd"e si cocnrende
...prof uncrosses fingers temporarily...
As far as "improved" is concerned, It wasn't too horrible to begin with. About once a day a release/renew fixed it. The only time it riled me up was when it would decide to drop out during a streaming audio/video presentation.
...crossing fingers again...
As fra sa im"porvd"e si cocnrende
...prof uncrosses fingers temporarily...
As far as "improved" is concerned, It wasn't too horrible to begin with. About once a day a release/renew fixed it. The only time it riled me up was when it would decide to drop out during a streaming audio/video presentation.
...crossing fingers again...
One thing I've noticed with the new firmware is that the lease time has been reduced from 24 hours to 12, even when set at "0", which supposedly equals one day. Hmmmm...
I've always wanted to set up an assigned IP address system. This looks like a good time to try it.
This is another case where two variables have changed at the same time (I moved to a new city and downloaded the new Linksys firmware shortly after I arrived), making it harder to diagnose the problem. I may try reverting to the previous firmware. If the problem goes away I'll know it's the firmware. If not, it's likely my new connection.
The setup was two PCs running through the router to the modem and out to the world.
Plug either in and both worked...just not at the same time.
Finally I changed the duplex setting on one PC from FULL AUTONEGOTIATION to Full Duplex 10 and the problem is solved.
Oh, and setting MTU back to 1500, it's stayed on, so far!
If that doesn't work I'm going to try the older firmware. Makes me kind of nervous about the security issues, though.
So far, so good. It does bug me to know there's a security risk involved. I've been thinking of going with a dedicated net server. Maybe now is the time.