been going on for the past couple of days.
certain sites and services work, while others won't... dns?
certain sites and services work, while others won't... dns?
anyone else having intermittent connection issues with roadrunner?
- Thread starter BlahBlahYouToo
- Start date
ya, I have that too. Usually there is a crew working on some problem down the road, then the next day we have problems with the cable/internet. So we call and they fix it but in a week or two its the same thing
It's been dring me nuts for the last month. Our ISP is roadrunner. We had a netgear router. Then all of a sudden, our internet connection had become on and off. Every time we had to unplug the router, then the modem, and replug them back in. And the problem would be fixed typically. Then one day, this solution stopped working. So we called time warner, they came over, checked, and said everything was fine. It should be the router's problem. So we bought a brandnew router (Linksys -Cisco WRT54GL Wireless-G Broadband Router). Then it worked without disconnection for a few days. Then the intermittent internet problem started again! So I called Linksys, and after several testings, they told me it was the ISP or my computers' problem!
I've been searching, asking, and trying to find a fix for a couple of weeks by now. Could anbody help me out? I'd really really appreciate your help!
BTW, the following response from another website seems to be a working solution, but the script mentioned in the post is missing...
"Had the same issue until I followed the following:
Reduce DNS errors in Windows 2000/XP
Windows 2000 and Windows XP come with a "DNS Client" Service that automatically caches (temporarily saves) DNS addresses. This boosts performance by avoiding repetitive DNS lookups of the same address -- the results of a successful lookup (positive response) are saved and reused until the cache expires.
By default the DNS Client also caches negative responses (including the lack of any response from the DNS server). Unfortunately, that can prevent you from recovering from transient DNS errors for an extended period of time. If, for example, the DNS servers at your ISP are temporarily overloaded, or slow to respond due to network congestion, the DNS Client will cache the negative response. Until that cache entry expires, which can take several minutes, it won't even try to lookup that name again -- you'll just get an immediate error. That prevents you from quickly recovering from DNS errors by simply retrying, the recommended thing to do. This can lead to frustrating delays and seeming loss of connectivity problems.
The best way for the typical Internet user to deal with this issue is to disable negative caching, leaving positive caching intact. (Completely disabling the DNS Client is like throwing the baby out with the bathwater because you would then lose the benefits of positive caching.) Negative caching can be disabled by adding three Registry Values (NegativeCacheTime, NegativeSOACacheTime, and NetFailureCacheTime, all not normally present), setting them to zero. Since manual editing of the Registry is a tricky and risky business, I've provided a simple Registry script to do the job. (Click the link to start the download; save the script to your desktop; and then double-click on it to run it. When you get the "Are you sure you want to add the information..." dialog box, click Yes. The script can then be discarded.)
There is no real downside to making these changes -- just delay if you make repeated tries to an invalid Internet name. (Nevertheless, please note that you do this at your own risk, and that it's always a good idea to back up your Registry before making any change.)
To go back to Windows default behavior, simply remove the three Registry Values described above. Since manual editing of the Registry is a tricky and risky business, I've provided a simple INF script to do the removal. (Click the link to start the download; save the INF file to your desktop; right-click on it, and then choose Install to run it. The INF file can then be discarded.)
For a more complete discussion and explanation of this issue, see "Broadband Tip: How to keep DNS Errors from slowing you down!
Note: I did not understand all of the above but............the problem has gone away.
"
Desperately,
mousetail
I've been searching, asking, and trying to find a fix for a couple of weeks by now. Could anbody help me out? I'd really really appreciate your help!
BTW, the following response from another website seems to be a working solution, but the script mentioned in the post is missing...
"Had the same issue until I followed the following:
Reduce DNS errors in Windows 2000/XP
Windows 2000 and Windows XP come with a "DNS Client" Service that automatically caches (temporarily saves) DNS addresses. This boosts performance by avoiding repetitive DNS lookups of the same address -- the results of a successful lookup (positive response) are saved and reused until the cache expires.
By default the DNS Client also caches negative responses (including the lack of any response from the DNS server). Unfortunately, that can prevent you from recovering from transient DNS errors for an extended period of time. If, for example, the DNS servers at your ISP are temporarily overloaded, or slow to respond due to network congestion, the DNS Client will cache the negative response. Until that cache entry expires, which can take several minutes, it won't even try to lookup that name again -- you'll just get an immediate error. That prevents you from quickly recovering from DNS errors by simply retrying, the recommended thing to do. This can lead to frustrating delays and seeming loss of connectivity problems.
The best way for the typical Internet user to deal with this issue is to disable negative caching, leaving positive caching intact. (Completely disabling the DNS Client is like throwing the baby out with the bathwater because you would then lose the benefits of positive caching.) Negative caching can be disabled by adding three Registry Values (NegativeCacheTime, NegativeSOACacheTime, and NetFailureCacheTime, all not normally present), setting them to zero. Since manual editing of the Registry is a tricky and risky business, I've provided a simple Registry script to do the job. (Click the link to start the download; save the script to your desktop; and then double-click on it to run it. When you get the "Are you sure you want to add the information..." dialog box, click Yes. The script can then be discarded.)
There is no real downside to making these changes -- just delay if you make repeated tries to an invalid Internet name. (Nevertheless, please note that you do this at your own risk, and that it's always a good idea to back up your Registry before making any change.)
To go back to Windows default behavior, simply remove the three Registry Values described above. Since manual editing of the Registry is a tricky and risky business, I've provided a simple INF script to do the removal. (Click the link to start the download; save the INF file to your desktop; right-click on it, and then choose Install to run it. The INF file can then be discarded.)
For a more complete discussion and explanation of this issue, see "Broadband Tip: How to keep DNS Errors from slowing you down!
Note: I did not understand all of the above but............the problem has gone away.
"
Desperately,
mousetail
i believe mine was the same issue. i had a netgear router. kept having to bounce the router.
while certain sites (AT) would continue to work, others wouldn't - at the SAME time AT was still working.
definitely DNS related.
since i use this machine 99.9% of the time, i unplugged the router and went direct into my pc and so far so good.
while certain sites (AT) would continue to work, others wouldn't - at the SAME time AT was still working.
definitely DNS related.
since i use this machine 99.9% of the time, i unplugged the router and went direct into my pc and so far so good.
whoa .. i have the exact same problem with roadrunner and i too have a netgear router.
my connection keeps on dropping and i have to restart the router everytime to make it work again...i thought my router has gone bad since its 4 years old ... but now i guess thats not the case
i'll try moustail's method and see if it works.
my connection keeps on dropping and i have to restart the router everytime to make it work again...i thought my router has gone bad since its 4 years old ... but now i guess thats not the case
i'll try moustail's method and see if it works.
Anubis
No Lifer
I have roadrunner as well, and while I love the throughput, I hate the reliability.
It seems to go down more often than any other ISP I've ever had-- and I wonder if it's how they structure their network. I notice through traceroute that a simple request to just about anywhere bounces around literally ten to 15 internal roadrunner routers before it hits a first-tier pipeline. If any one of these routers has an issue (and they seem to have issues frequently), then your internet connection just went down...
It seems to go down more often than any other ISP I've ever had-- and I wonder if it's how they structure their network. I notice through traceroute that a simple request to just about anywhere bounces around literally ten to 15 internal roadrunner routers before it hits a first-tier pipeline. If any one of these routers has an issue (and they seem to have issues frequently), then your internet connection just went down...
so still no solution guys??
BTW, I found the script, and ran it, BUT IT DIDN'T SOLVE MY PROBLEM AT ALL! The connection still gets dropped once in an hour or so. The terrible part is that we have a VOIP phone, which is basically useless
Here's the script if you want to try:
http://cable-dsl.navasgroup.com/dns_cache.htm
Please let me know if you find a solution that works!!!!!!!!
BTW, I found the script, and ran it, BUT IT DIDN'T SOLVE MY PROBLEM AT ALL! The connection still gets dropped once in an hour or so. The terrible part is that we have a VOIP phone, which is basically useless
Here's the script if you want to try:
http://cable-dsl.navasgroup.com/dns_cache.htm
Please let me know if you find a solution that works!!!!!!!!
TRENDING THREADS
-
Discussion Zen 5 Speculation (EPYC Turin and Strix Point/Granite Ridge - Ryzen 9000)- Started by DisEnchantment
- Replies: 25K
-
Discussion Intel Meteor, Arrow, Lunar & Panther Lakes Discussion Threads
- Started by Tigerick
- Replies: 21K
-
Discussion Intel current and future Lakes & Rapids thread- Started by TheF34RChannel
- Replies: 23K
-
-
Facebook
Twitter