Re: CNET.com
From: Robert Aldwinckle (robald_at_techemail.com)
Date: 01/15/05
- Next message: Ravi Prasad: "Need to always refresh page to get to a page first time"
- Previous message: XPUSER: "Re: MSXML 4.0 SDK"
- In reply to: Mike: "Re: CNET.com"
- Next in thread: Mike: "Re: CNET.com"
- Reply: Mike: "Re: CNET.com"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 14 Jan 2005 20:51:10 -0500
"Mike" <Mike@discussions.microsoft.com> wrote in message
news:DE70B3E8-F718-4073-B2CC-683E960D0ABA@microsoft.com
...
> I thinking if I go the http://i.i.com.com I should get that page but I
> get "The page cannot be displayed" If I can't get the page to display then I
> won't be able to download the .gif files.
>
> I'm I looking at this correctly?
I doubt it. That name is an alias for a caching server.
I don't think there would be any reason for it to have
a "default" page.
In fact, I just tried it. It returned "Invalid URL..."
You didn't answer PA Bear's question but I'll take a chance
that you have NTx. If not you won't have nslookup and
will have to check that your HOSTS file isn't causing any
interference in the lookups. Renaming it would avoid that
issue.
Does your DNS show you that alias?
Open up a command window and enter:
nslookup i.i.com.com
<nslookup output>
Non-authoritative answer:
Name: a868.g.akamai.net
Addresses: 132.246.2.7, 132.246.2.8
Aliases: i.i.com.com
</nslookup output>
Next, is something blocking that site?
Enter this command:
ping i.i.com.com -n 1
Believe it or not that worked for me. Amazing. I was expecting
to see ping (ICMP packet) blocked. But the main point of trying it
is to see if *your lookup* is bypassing the DNS and getting an
invalid address, either from your HOSTS file or from your dnscache,
which would be different from any of the addresses returned by
nslookup.
>
> Thanks for your help!
>
> Mike
HTH
Robert Aldwinckle
---
- Next message: Ravi Prasad: "Need to always refresh page to get to a page first time"
- Previous message: XPUSER: "Re: MSXML 4.0 SDK"
- In reply to: Mike: "Re: CNET.com"
- Next in thread: Mike: "Re: CNET.com"
- Reply: Mike: "Re: CNET.com"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|