Re: Instead Windows Update I get Google

10 Mar 2009 10:10 PM

Robert Aldwinckle

(cross-post added to XP Networking)

"Sue" <S**@discussions.microsoft.com> wrote in message news:4E1E096C-6897-44B4-B65C-2EADF2A9740C@microsoft.com...
> "elvis" wrote:
>
>> When i'm trying to get into Windows Update site it enters Google.
>> someone knows what can I do?

The ISP could be doing that when the host name entered
is unknown.

Show quoteHide quote

>
> Here are some things I discovered at my parents' house on their wireless
> network (Linksys router, cable modem):
> 1. two of their computers had the same problem (1 laptop, 1 desktop, both XP)
> 2. my XP laptop, which never had this problem, suddenly did
> 3. my sister came over with her Mac, and had the same problem
> 4. when I went home to my own wireless network (same brand/type of router),
> my laptop no longer had that problem
>
> Points 3 & 4 add an interesting dimension to the problem. Perhaps someone
> can figure it out.

11 Mar 2009 12:37 AM

Sue

"Robert Aldwinckle" wrote:

> (cross-post added to XP Networking)
> "Sue" <S**@discussions.microsoft.com> wrote in message news:4E1E096C-6897-44B4-B65C-2EADF2A9740C@microsoft.com...
> > "elvis" wrote:
> >
> >> When i'm trying to get into Windows Update site it enters Google.
> >> someone knows what can I do?
>
>
> The ISP could be doing that when the host name entered
> is unknown.

The url was http://update.microsoft.com whether entered directly or through
the ms homepage.

Show quoteHide quote

> >
> > Here are some things I discovered at my parents' house on their wireless
> > network (Linksys router, cable modem):
> > 1. two of their computers had the same problem (1 laptop, 1 desktop, both XP)
> > 2. my XP laptop, which never had this problem, suddenly did
> > 3. my sister came over with her Mac, and had the same problem
> > 4. when I went home to my own wireless network (same brand/type of router),
> > my laptop no longer had that problem
> >
> > Points 3 & 4 add an interesting dimension to the problem. Perhaps someone
> > can figure it out.

11 Mar 2009 1:27 PM

Robert Aldwinckle

Show quote Hide quote

"Sue" <S**@discussions.microsoft.com> wrote in message news:C84FB7A2-D2A1-4347-A7F6-EC29261410A6@microsoft.com...
>
>
> "Robert Aldwinckle" wrote:
>
>> (cross-post added to XP Networking)
>> "Sue" <S**@discussions.microsoft.com> wrote in message news:4E1E096C-6897-44B4-B65C-2EADF2A9740C@microsoft.com...
>> > "elvis" wrote:
>> >
>> >> When i'm trying to get into Windows Update site it enters Google.
>> >> someone knows what can I do?
>>
>>
>> The ISP could be doing that when the host name entered
>> is unknown.
>
>

> The url was http://update.microsoft.com whether entered directly or through
> the ms homepage.

It's good to see that you were using a protocol prefix.
Often not doing that is part of the problem cause.
But how sure are you that there was a successful lookup
done for that host name?   E.g. did you try using nslookup
with it in a Command Prompt (aka cmd.exe window)?

Also, just doing that may not be a sufficient check
because Fiddler2 would show you that there would be
an immediate redirect, depending on the User-Agent
the browser sent with the first request and then the same
problem could occur with a subsequent lookup.

You can see some of this, e.g. without giving a User-Agent,
simply by using telnet.   E.g. start telnet.   Then issue:

    o update.microsoft.com 80

Wait for the cursor to show at the top of the screen
and type:

    GET /

Then press Enter.

FWIW here is what I see from that.

<telnet>
HTTP/1.1 302 Object moved
Date: Wed, 11 Mar 2009 13:13:45 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Location: /windowsupdate/v6/default.aspx
</telnet>

So, doing that would at least test the initial lookup
that you were getting from whatever your nslookup
would be showing you.

Etc.

HTH

Robert
---

Show quoteHide quote

>
>
>
>
>> >
>> > Here are some things I discovered at my parents' house on their wireless
>> > network (Linksys router, cable modem):
>> > 1. two of their computers had the same problem (1 laptop, 1 desktop, both XP)
>> > 2. my XP laptop, which never had this problem, suddenly did
>> > 3. my sister came over with her Mac, and had the same problem
>> > 4. when I went home to my own wireless network (same brand/type of router),
>> > my laptop no longer had that problem
>> >
>> > Points 3 & 4 add an interesting dimension to the problem. Perhaps someone
>> > can figure it out.
>