(interleaved reply elaborates on previous remarks)
Luis Filipe said:
Hello
It is a little complex for me what you're explaining. Could you pls describe
those steps for a guy with less knowledge about internet?
The only thing I know is that I can use telnet and nslookup in the prompt
windows.
But I don´t know what for.
Thank you
Luis
Enter in the cmd window:
telnet pinnaclesys.com 80
Wait for the screen to clear and start typing at the top:
GET /
(That's GET<space><slash><Enter>. You will not be able to see your typing.)
Here are the first few lines of what I see when I do that:
<example>
HTTP/1.1 302 Object moved
Date: Tue, 15 Nov 2005 16:25:15 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Location: /publicsite/us/
</example>
The first line shows that the server *assumes* that the connection
is HTTP 1.1 protocol; so if you don't have that set in your Options
Advanced tab, try changing it.
The last line that I quoted shows that you might get a better or at least
faster connection by avoiding the redirect by entering this full URL
in your Address bar:
http://pinnaclesys.com/publicsite/us/
In fact, evidently there is yet another redirect somewhere because
here is what ends up in the Address bar after I tried that:
http://pinnaclesys.com/PublicSite/us/Home/
If instead (after a *long* wait) you get an error message,
post the error message. That would be proof either that
your DNS doesn't know this lookup or it is getting the wrong address
or the site is blocked for you for some reason.
You could use nslookup to check on the lookup:
E.g. enter in your cmd window:
nslookup pinnaclesys.com
When I do that here is the lookup:
<extract>
Non-authoritative answer:
Name: pinnaclesys.com
Address: 198.37.36.40
</extract>
If you are blocked you might get some clues about that from tracert
E.g. enter in your cmd window
tracert pinnaclesys.com
Mine gets this far before it is blocked:
<example>
11 1652 ms 1357 ms 1974 ms dcr2-so-2-0-0.SanFranciscosfo.savvis.net [204.70.192.90]
12 1666 ms 1322 ms 1509 ms bhr1-pos-0-0.SantaClarasc8.savvis.net [208.172.156.198]
13 1392 ms 1330 ms 1604 ms csr2-ve243.SantaClarasc8.savvis.net [66.35.194.51]
14 1589 ms 1603 ms 1329 ms 66.35.202.86
15 * * * Request timed out.
</example>
I'm not worried about this being blocked because tracert uses the same
kind of ICMP packet that ping does and that protocol is often blocked
by large companies as a defense against moronic denial of service "exploits".
You don't really need a definition of canonical name to figure out
that I mean the other (non-alias) name here.
....