....
I did as you suggest and i still get "unknown zone"
Is the site still being listed in your Trusted sites list?
Try removing it as well, otherwise changing the Internet zone
settings might not have an effect.
I suggested using High because it was the simplest change.
What I would normally try myself is setting everything to Prompt.
As I mentioned:
If you like try setting prompts and see if you at least get a prompt.
Something else I just noticed is that before I get the first prompt
the background of the page changed to that olive green or whatever it is.
That would be proof too that you have *some* connectivity with that site.
The diagnostics are deficient because we don't know if your browser
is seeing *anything*. E.g. if it is getting something up to the first two
prompts which is preventing rendering (such as a problem with your
Shockwave Flash extension) that would be one thing.
However, it could be a case of a DNS problem which would show
you exactly the same end diagnostic. You need to use supplemental
diagnostics to determine exactly what is going on in order to figure out
what to adjust. The ultimate tool is a packet sniffer but most people
don't have one and even fewer people know how to use them.
Let's check the DNS because it is the next easiest thing to do
and you haven't made clear if you are getting the name resolved
to an IP address.
Open a command window (e.g. Run... cmd) and use it
to test connectivity with that site.
Do either of the traditional connectivity test tools (e.g.
ping or tracert) show you an IP address for that site?
E.g. enter
ping -n 1
www.elmomc.com
or
tracert
www.elmomc.com
(Press Ctrl-c to terminate the tracert because it is only
the address resolution function of the command that we
are interested in.)
If neither of those can show you an IP address for that site
you have some kind of DNS problem with it.
ping -n 1 wwww.elmomc.com
Ping request could not find host wwww.elmomc.com. Please check the name and try again.
Tracing route to
www.elmomc.com [199.203.1.129]
</example>
So apparently I have some kind of problem with it for the first lookup.
Such a delay could be what is causing your IE its symptom.
If you do get an IP address showing for either of those
commands which is different from the one in my example
then either you are getting an override from your HOSTS file
(which Frank asked you to check) or from your dnscache
which you could clear with
ipconfig /flushdns
but it might also be the case that your DNS isn't finding
that site quickly enough or worse giving you the wrong
address which doesn't have an open server.
So check your DNS lookup with nslookup:
nslookup
www.elmomc.com
If that times out enter instead:
nslookup elmomc.com
(i.e., the domain name, and then try the first command again.
Alternatively, enter just nslookup (by itself without operands)
to enter its interactive mode and enter that server name and
that domain name to test them. Enter the exit subcommand
to end the nslookup interactive session and return to the normal
command line.
There is more that you can do with nslookup in its interactive mode
to find a site's address but let's start with that. Recently I have had
to resort to the domain name trick myself several times to find some
of the sites that others have reported having problems with.
Good luck
Robert
---
