Re: Why can't I access microsoft.com
From: removethis (_at_minot.com)
Date: 05/01/04
- Next message: r.: "Tools > Internet Options > History"
- Previous message: r.: "Tools > Internet Options > General > Home Page"
- In reply to: *Vanguard*: "Re: Why can't I access microsoft.com"
- Next in thread: C. A. Upsdell: "Re: Why can't I access microsoft.com"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 1 May 2004 10:14:13 -0500
Thanks Vanguard for the help you have posted. I too, am having problems
getting to www.microsoft.com. I have also tried all of the things you
mentioned below, but no luck. I WAS able to get to the site when I went
through urlencoded.com, but not directly.
Here is a little twist for you. I have two computers setting side-by-side,
connected to the same network, running the same software and OS (XPPro).
One can get to the microsoft web site, the other cannot. So, it can't be
the ISP or my network.
Any other suggestions?
Thanks,
Bill
On Sat, 1 May 2004 05:00:19 -0500, *Vanguard* wrote:
> "anonymous@discussions.microsoft.com" said in
> news:6eb301c42f3d$b1c6c1c0$a101280a@phx.gbl:
>> I did formate of my hard drive and re-installed the
>> windows 98 second edition operating system then upgraded
>> to xp. I did a fresh install I thought.
>
> Well, that's not really a fresh install. That's tagging along
> everything that was defined for Windows 98, including registry entries
> that might not be valid or used under an NT-based version of Windows.
> You don't need Windows 98 to be installed in order to install the
> Windows XP upgrade. In your case, a fresh install would have been: (1)
> Boot using the Windows XP installation CD; (2) Have its install delete
> the partitions (since you formatted anyway) and then create a new one
> for Windows XP; (3) Swap in the Windows 98 CD when prompted to verify
> that you qualify for the upgrade version of Windows XP; and, (4)
> Continue the pure install of Windows XP. It's up to you if you want to
> go through the entire install again. Upgrading within the same kernel
> architecture is okay, like Windows 95 to 98 to ME or Windows NT to 2000
> to XP, but calling the migrate from a DOS-based (plus 32-bit API) kernel
> version of Windows to the NT-based version an "upgrade" is, to me, a
> misnomer. It's not an upgrade. It's a migration. But some folks don't
> have the time for a clean install, especially for all the applications,
> and it seems easier to do the "upgrade" to them (but this migration
> usually ends up with problems later).
>
>> I'm not sure what you meant by purging my internet
>> browser.
>
> Assuming you are using IE: Tools -> Internet Options -> General tab ->
> Delete files (including offline content).
>
>> I typed in www.microsoft.com in the address bar than
>> enterand that is when I get the page I mentioned earlier.
>
> See if your DNS server has a lookup for the IP name:
>
> nslookup www.microsoft.com
>
> You should get back an IP address, if not several, for that IP name. If
> you don't get back any IP addresses (i.e., it cannot find a record for
> the IP name of www.microsoft.com) then you have a DNS problem. If you
> get info, you may see aliases returned which list www.microsoft.com and
> another weird looking one for www.microsoft.akadns.net. I know
> Microsoft is using Akamai Technologies for their Windows Update service
> but I'm not sure why they need to have an alias to their domain. This
> seems something new to me (I don't remember seeing the adadns.net alias
> before).
>
> See if you can telnet to the web site. In a DOS shell, run:
>
> telnet www.microsoft.com 80
>
> It's not important what you see, only to check if you actually get a
> connection. You'll probably just get a blank screen (it's waiting for
> you to login). Just enter "bye" to quit the session (or just close the
> DOS shell window). If you get an error about the IP name, host not
> found, no response or a session timeout then the problem really isn't
> with the web browser.
>
> I might have suggested pinging the web site to check if you have a good
> route to them through the Internet but Microsoft disables ping on almost
> all their hosts. So instead do a traceroute to check if you can
> actually get to them:
>
> traceroute www.microsoft.com
>
> You'll probably get to some *.msn.net boundary host that won't permit
> you to penetrate further into their network (so you'll see a bunch of
> lines with "* * * Request timed out").
>
> See if you can use their IP address with your web browser to open their
> web page. Use a URL of:
>
> http://207.46.134.221/
>
> Although this is the akadns.net alias, it should work to open
> Microsoft's web page. Otherwise, try other IP addresses that got
> returned from the nslookup command.
>
>> "Have your checked your hosts file to ensure it isn't
>> blocked (by having a "127.0.0.1 <ipname>" entry)?
>
> The hosts file (without an extension name) is in
> C:\Windows\system32\drivers\etc. If you open it in Notepad, check what
> uncommented lines there are in it. Then report them here. The format
> for the mappings are:
>
> ipaddress ipname [# optional comment]
>
> You probably have:
>
> 127.0.0.1 localhost
>
> in the file. But also check if there is an entry like:
>
> 127.0.0.1 www.microsoft.com
>
> If so then you'll end up entering www.microsoft.com but end up going to
> 127.0.0.1 which is the hardcoded internal IP address for your own
> computer, and you're not running Microsoft's web server so there's no
> web page to display.
>
> Windows 2000/XP runs a local DNS client that will cache up some records
> (of IP name to IP address mappings). For giggles, purge it by running
> in a DOS shell:
>
> ipconfig /flushdns
>
> and then see if you still cannot get to www.microsoft.com.
>
>> I even did the Spybot that I read about in this
>> disscusion group. But nothing was found.
>
> You should run both Ad-Aware and Spybot. They don't update their
> signatures at the same pace and sometimes one product will find
> something that the other missed. You also need to run CWShredder. The
> HijackThis utility is daunting if you don't understand what it lists.
> It doesn't fix anything unless you choose to do so which means you have
> to understand the items it displays. Usually afflicted users simply
> post the HijackThis log to a newsgroup and ask others if they see
> anything suspicious.
>
> Have you tried adding *.microsoft.com to the Trusted Sites security zone
> yet? I don't recommend doing this permanently but it will load that
> site without all the restrictions and protection of the Internet
> security zone. If you have a popup blocker or other browser complement
> utilities, they often will ignore their filtering on trusted sites.
>
> If after all this you still cannot get to www.microsoft.com, see if
> browsing to them through a different route gets you there. In your
> browser, enter:
>
> http://www.urlencoded.com/
>
> to use this freebie web-based anonymous proxy service. This is a public
> proxy and I never trust them but will use them if nothing else works.
> They have NO privacy policy so don't navigate anywhere you consider
> sensitive (but then no public proxies that I've looked at had a [good]
> privacy policy). There are lots of other public proxies but most
> require you to configure your browser's settings to go through their
> proxy. This one gives you a web interface so you don't have to
> reconfigure anything in your browser. Most of them only permit HTTP
> connections (which is what you need for a web site) but many will not
> support any other protocol, like FTP, because they don't want their
> proxy deluged with huge file transfers, so public proxies have their
> deficiencies.
>
> The point is not to anonymously browse to Microsoft but to slide
> sideways in a working route to urlencoded.com which then most likely has
> a different route than you do to www.microsoft.com. If you can get to
> urlencoded.com (or other sites which you say you can) then your computer
> is probably okay. If their route to that site doesn't work then it's a
> problem with Microsoft or an upstream host that is common to you and to
> urlencoded.com. If it works from urlencoded.com then the problem is
> with your ISP. It is possible that your route through your ISP is dead
> to Microsoft. Routes are not as dynamic as users think. Basically
> whatever your ISP's router says to use is what you get (and whatever the
> next one says is what you get, and so on, and none of them try another
> route just because you couldn't reach a host). If you cannot reach a
> host, the router doesn't go dynamically hunting around for another path.
> That usually requires you calling your ISP to tell them that you cannot
> get to a site and you suspect a dead route. You might think there would
> have already been lots of their users complaining about not being able
> to get to Microsoft. I've seen people running out of a burning
> apartment complex and asked if anyone called the police but everyone
> says no because they figured someone else called. I've called the power
> company almost an hour after an outage and found I'm the first caller.
> I've found students piled up at a classroom door figuring it was locked
> (because the first student was parked outside), walked up to door,
> opened it, and walked right in and had the rest of the class follow in.
>
> Have your called your ISP yet to report the inability to reach
> www.microsoft.com? It is also possible they run a cache proxy which
> caches up web pages, and if their cache proxy is screwed up then you
> can't get to that site (you have no way to force a flush of their
> cache).
>
> While you do not run a firewall (not a smart thing when dealing with the
> Internet; even the crippled firewall in XP is better than nothing), do
> you use a router which has a firewall? Have you checked that the web
> site isn't blocked in there?
- Next message: r.: "Tools > Internet Options > History"
- Previous message: r.: "Tools > Internet Options > General > Home Page"
- In reply to: *Vanguard*: "Re: Why can't I access microsoft.com"
- Next in thread: C. A. Upsdell: "Re: Why can't I access microsoft.com"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
