Hi all! I have this weird problem with some websites e.g. www.ascensionhealth.org. When i try to browse this site it just keeps on giving me the status connecting to www.ascensionhealth.org but it dies later. To check if this website is up or down I used another ISP and yes the websites just showed up and worked fine. Could it be dns problem? By the way.. I did a traceroute to this sites with the 2 different ISP but the results were the same, some nodes give a request timed out. But what confuses me is that my other ISP can browse the said website but the other cannot. What do you think is the problem? I need some explanation. Thanks!

Is the site's IP address a bogon? There are some IP ranges that used to be private or experimental but were added to the ranges of IPs that are public. Some DNSes may not be configured properly with the new ranges.

This is the equivalent IP(198.184.142.231) of that site! I guess it's not a bogon IP. Any other ideas? Why is it that my other ISP can connect with the website with no problem?

I mistyped the host commands address and then my route acted up before I could correct my last post.

Does the connection time out if you enter the commands: "host www.ascension.org" or "traceroute www.ascension.org"?

If they mention an IP address then it isn't a DNS issue.
After finding it in a google search, I was able to access the site directly. In Firefox, I got a graphic front page. In konqueror, I got a flash movie.

Can you reach the website using the IP address instead?
If so, does a different browser work?

If it is just Firefox that is giving you a problem and it starts getting stuff but times out, try increasing the value of
about:config -> network.http.keep-alive.timeout

nope..

any browser won't make it with my current ISP.


By the way, my problem now is solved I have the proxy server of my ISP. But the question remains, what could have caused my problem?

Thanks man!

If you had a very old kernel, there used to be a feature ( based on a RFC document ) where the kernel would dynamically adjust some sort of window. However, some gateways in the net used a version of MS Windows that caused the traffic to crawl as a result. This feature was later removed from the kernel. I'm afraid I don't remember what is was called, but it shouldn't be the cause in your case.

Is there anything in common in the sites that were affected? Do they all use flash animations, for example?

Some sites have flash on them... but one thing is clear now it's not a DNS problem..

Try lowering your MTU setting, the default is 1500, try lowering to 1492 and keep lowering till the site fully works.

Craig