ip-address of download.microsoft.com

hi,

can anybody tell me the ip-address(es) of download.microsoft.com
?

thanks

Salutations *QuadX* !
Dans http://groups.google.fr/groups?threa...TNGP10.phx.gbl
tu nous disais :
> can anybody tell me the ip-address(es) of download.microsoft.com ?

C:\>ping download.microsoft.com

Envoi d'une requête 'ping' sur ===> a767.ms.akamai.net [69.45.86.57]

Cheers

--
~Jean-Marc~
Contact : http://msmvps.com/docxp/contact.aspx
Site : http://perso.wanadoo.fr/doc.jm/ http://docxp.mvps.org
WebLog : http://msmvps.com/docxp/

thank you.

can't find this address in the hosts-file or the restricted sites
zone of ie though. a nslookup gives the same result as voor the
full name. unreachable from my machine. ping did work!

>>>
~Jean-Marc~ wrote:
> Salutations *QuadX* !
> Dans
> http://groups.google.fr/groups?threa...TNGP10.phx.gbl
> tu nous disais :
>> can anybody tell me the ip-address(es) of
>> download.microsoft.com ?
>
> C:\>ping download.microsoft.com
>
> Envoi d'une requête 'ping' sur ===> a767.ms.akamai.net
> [69.45.86.57]
>
> Cheers

"QuadX" <> wrote in message
news:
....
>>> can anybody tell me the ip-address(es) of download.microsoft.com ?

>> Envoi d'une requête 'ping' sur ===> a767.ms.akamai.net [69.45.86.57]

> thank you.
>
> can't find this address in the hosts-file or the restricted sites
> zone of ie though.

Don't look for the address. Look for the names:
download.microsoft.com
and
a767.ms.akamai.net

Actually while you are testing it would be best to rename HOSTS
and clear your dnscache just to take old data out of the equation.
E.g. after renaming HOSTS in your command window enter:

ipconfig /flushdns


> a nslookup gives the same result as voor the full name. unreachable from my machine. ping did work!

I have seen that. I have also seen tracert resolving a name
to an address when ping can't. I have speculated that perhaps
there is a different wait for address resolution between the commands.
And in that case perhaps the wait for address resolution for IE is
significantly shorter than the others. Then a possible circumvention
to slow resolution may be making ping or tracert do the lookup
which would then be cached by dnscache.

I have also seen cases where no address resolution was possible
until I went in with nslookup and switched to the domain's name
server (which may be listed by using nslookup's set type=any)
Doing a lookup with that seems to be enough to make my DNS
sufficiently aware of the address for IE to use it. Etc.


BTW what address did your ping get? If it was an old address
there might be a server there doing something different now
but still replying to ping. A better connectivity test for http
connections is to try telnet to the server's port 80.
If the telnet screen clears there is a server listening there.
You may actually be able to see the first response by typing GET /
(That's GET<space><slash><Enter>. Unless you activate telnet's
localecho you won't see what you are typing.)


HTH

Robert Aldwinckle
---