MMD said:
I have this problem sporadically but I can't get to a
website I have hosted on "(e-mail address removed)".
That's an E-mail address you are showing us.
What is the URL that you are having trouble with?
Also make sure when you use it that you provide a proper protocol
prefix to try to avoid any confusion with the AutoSearch feature.
FWIW whenever I have trouble connecting to a site here is what I do.
Switch to a command window and enter:
nslookup
Without options nslookup just tests your DNS server addresses.
If they aren't working that explains why you can't connect.
Next I enter the server name. (See my question above about what your
URL is for your web site). E.g. if the web site I was trying to open was
http://bucks.com/ then I would enter bucks.com for nslookup to resolve
into an IP address. In fact, here is what I get when I do that:
<example>
Non-authoritative answer:
Name: bucks.com
Address: 63.240.105.137
Aliases:
www.bucks.com
</example>
And if that step didn't work that would explain a problem symptom too.
Notice that
www.bucks.com is an alias for the domain name.
Sometimes that seems to be an issue for some DNS servers.
I have speculated that perhaps they don't retain a list of aliases
and have to do extra requests of their own to adjacent and even
more remote DNS servers to resolve the alias name. In any case,
it seems that resolving alias names can take more time than
it takes to resolve the corresponding canonical name. And then
the next time you request it especially if you request it right away
it takes less time. I have suggested that that might be a useful
workaround as a way to prime the lookup for IE's attempt.
Next, I would like to know if there is an open port 80 on that server.
To do that I use telnet. For example:
telnet bucks.com 80
If the screen clears that means the port is open.
If there is a timeout that means either that there is no open port
or that there is no path to that server.
To check the latter you could use first: ping -n 1
ping -n 1 bucks.com
If that works there is at least a path to that server for ICMP packets.
If it doesn't work it unfortunately doesn't mean much any more
because many large sites now inhibit ICMP packets to guard
against the moronic Denial of Service "exploits" that the Internet
has been plagued with.
You can try to find out how far the ping gets by using tracert
tracert bucks.com
Again, it doesn't help a lot with your problem of getting an HTTP
connection working but at least it can tell you something about
the path to the server and if you have previously done it while
the server was working for you it may even give you some useful
clues about whether your ISP or the site was to blame for your
poor service.
Note that none of this has anything to do with IE and I am not
a networking expert. So if you need more detailed help you
may be better off posting your query to a newsgroup which
specializes in networking for your OS.
HTH
Robert Aldwinckle
---