Discussion Locked

internet connection time out part 2

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi,

I've have recently posted a question about how my internet connection gets drop when idling for 3 minutes. I found out that the router is not responding right away. There's a 30 to 40 seconds delay when IE is launched and during the period pinging the router will get no responce, instead it will timed out for 30 to 40 seconds then it will start replying. I've noticed that this happens to most of the computers (clients and servers, dynamic and static IPs), there are about 5 computers, including servers that don't have this problem. I have been trying to troubleshoot this problem for about a week now but can't seem to find where the problem lies. My guess would be the router since it's not responding to clients request but then there are the few that do work.

Earthlink, our ISP would not help with the problem because they say we managed our own router. And I'm kinda new here so I'm not too familiar with this router and the configuration. I want to make sure it is the router that is defective before I start replacing hardware. Has anybody experienced similar problem or have any way to isolate this problem?

By the way, the router is a speedstream 5851 by Efficient Network and we have a sdsl account with earthlink. I havetried updating the firmware for the router but there are none, atleast I can't find any. The current firmware for that router is 4.1.0. Please help, this problem is driving me nuts!

7 replies

by cg it

How many hops are listed (hop meaning # of routers the message has to go through? (lower the # the better, but reflect the actual # of routers the message has to go through.

by eminent87

If I do a tracert to the router it only takes one hop. But I'm not sure where you're going with this since there is only one router and the connection between the clients and the router drop during idling. Once the router respond then everything is fine for a couple of minutes.

by ann777

You need to find the manual for the router and figure out how to optimize the delay and other settings for your sdsl account. Earthlink should be able to help you do this, but may not want to because of the fact that the previous persons there reconfigured the router; they don't want to be responsible for changing anything and something else not working properly.

Find out how to print the current configuration in the router and then go from there. Figure out which lines in the configuration have to do with sync'ing communications and then question Earthlink as to how they might change it to more correspond with their standard sdsl configurations. Assure them that you have a current printout of the current configuration and that youwill not hold them responsible unless the hardware ceases to function at all. See if they'll help then.

by eminent87

Although your answer didn't solve my problem but it did lead me in the right direction. To make a long story short, I found out that it was the sonicwall that was causing the problem, after upgraded the firmware all the settings changed and caused the mix up with router. I also had ppl at efficient configure some changes to the router too because the previous person who configured it didn't configured it correctly.

Thanks for everyone's effort in trying to help me resolve this issue.

by georgevlob

I do not know what type of internet connection you have, but it sound like you may have to modify the MTU size. Microsoft sets this to 1500, but some protocols like PPPoE have a maximum MTU size of 1492. The key to this is to set the MTU size as high as possible without getting errors. Usuanlly anywhere between 1450 and 1492 will work fine. You can modify the setting in the Registry in the following key:

KEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\[The
ID for the adapter]\

If the MTU key does not exist, create it as REG_DWORD with the key value equal to the MTU size.

This discussion is closed to new replies.