beavxx
join:2000-11-09
Kenosha, WI
| page cannot be displayed-WI.rr.com
SE Wisconsin Roadrunner. My friend's PC shows page cannot be displayed after browsing and hitting the back button as well as when clicking on good working links. This happens way too frequently. Tried a MS solution of cleaning temp files, history, cookies, etc. No luck. Any Ideas out there???
Thanks |
|
2kmaro
Think
Premium,ExMod 1 BC
join:2000-07-11
ColossalCave
clubs:  
| We assume, since you tried MS solutions, that your friend is using Internet Explorer as the browser.
One thing to try right off to find out if it is an IE problem or something else would be to load up another browser such as Firefox or Opera and see whether or not he has the same problem(s) with a different browser.
Loading Firefox or Opera will not affect installation of IE at all - perfectly acceptable to have 2 or more on your system at the same time.
Once past that hurdle, post back with the results of the test.
Has he run any type of line quality tests (as we have available here at BBR) or tracerts to the places he's having trouble with?
--
then think again! |
|
dwlamborg
join:2000-09-27
KC, MO | reply to beavxx
The I.E. message "page cannot be displayed" can have many causes. Take a look at the various MS KB articles here: »tinyurl.com/43bkd |
|
Mele20
Premium
join:2001-06-05
Hilo, HI
| reply to beavxx
Probably DNS issues because of the new speed. I see that a lot now on Hawaii RR usually during prime time 4PM -11PM. Users in other franchises are reporting the same problem since the speed increase.
You might try this:
»ntcanuck.com/
--
The first and foremost function of our jurors is to protect private citizens from a tyrannical and intrusive government...Jurors are the last line of defense for liberty. Thomas Jefferson 1789 |
|
beavxx
join:2000-11-09
Kenosha, WI
| I had some DNS problems also, changed the dns, worked for me. I was not getting page cannot be dislplayed, rather my URL lookup times were extended. Duh, we live in the same town, should have thought of changing the DNS right off the bat.
Thanks for the advice. I'll try it and post. |
|
beavxx
join:2000-11-09
Kenosha, WI | reply to beavxx
I changed my DNS server addresses, bingo, fixed. |
|
nobdumbtechs
join:2005-02-11
Milwaukee, WI | How bout a ping test, and speed test? Look at the modem lights to see if there is any problems. |
|
LLaffer
join:2001-01-25
Lenexa, KS
clubs: | reply to beavxx
I've had a similar problem, until I realized that PeerGuardian was blocking my access to TW web sites.
Makes sure he's not running it, or other "firewall" programs.
--
-Larry Laffer |
|
nobdumbtechs
join:2005-02-11
Milwaukee, WI
| Where are you guys getting these DNS info from? Where are you inputting the DNS. You got a router doing Domain Name Service, or what?
If you have a Router, just set everything to DHCP, automatic connect with auto DNS. This setting is safe and easy to use. Messing with it could cause undesire effects.
DNS in network settings or routers: If you find your DNS to be slow, contact your service provide tell them to get the crap fix, or upgrade to faster/more equiptment. Using a different DNS for the time being. Hope that you're not congesting that one too.. |
|
grasshopper
join:2003-04-07
Port Byron, NY | Contacting the service provider (Road Runner) will do about as much good as complaining about glaciers. Treewalk fixed the problem for me. RR support just had me do all the things I had already done, as usual. Solved NOTHING!!!!! |
|
Hart
join:2002-07-18
Hartland, WI
| I contacted the RR national help desk to report the slow DNS problem and the resulting network latency. The tech had me run a speed test, which yielded 4300 bps down. This was at 1:00 P.M. He concluded there was no problem and told me to call back if a speed test registered below 1500 bps. I explained that the slow DNS lookups were occurring between 4:00 P.M. and 11:00 P.M. and on weekends. I went on to say that all the bandwidth in the world would not solve a latency problem if the domain name servers could not return timely queries, i.e., long query times give the impression of a slow network in spite of having sufficient bandwidth.
Here's how I illustrated the problem. My e-mail app is set up to check six accounts every thirty minutes. Watching the activity window, it takes less than two seconds total to check for new mail on all the accounts during morning hours. In the evening it regularly takes close to a minute and sometimes even times out. If the server DNS name (pop-server.wi.rr.com) is replaced with its IP address in the account setups, the mail checks are back down to two seconds or less. Change it back and things slow down again. One can conclude: (a) there are not enough domain name servers to handle the evening load, or (b) there is not enough bandwidth on the facilities to the domain name servers, or (c) the network--routers, switches, facilities-- are misconfigured.
I've also noticed that many times my web browser appears to be stalled but when looking at the status bar at the bottom of the page it says "Looking up some.URL.com". Finally the page loads after the URL is resolved.
Another experiment I tried (as have others) was to substitute Verizon's domain name server addresses in place of Roadrunner's on my router. Here again the DNS queries returned back to "normal". Changed them back to Roadrunner's and things again bogged down.
Using the Unix dig DNS lookup utility, I tried several queries to pop-server.wi.rr.com and dslreports.com during the worst evening hours. Many of the queries were in the twelve to twenty seconds range and a few timed out with dig reporting unable to resolve.
It's been about a week since I talked with TW Roadrunner and query times appear to have improved, especially in the last three days or so. I hope they have found and fixed the problem.
-cisko |
|
