"Richard in AZ" <me@mailinator.com> wrote in message
news:ez%23QbfZ0HHA.5884@TK2MSFTNGP02.phx.gbl...[color=blue]
>
> "Mr. Arnold" <MR. [email]Arnold@Arnold.com[/email]> wrote in message
> news:%23jk70$X0HHA.748@TK2MSFTNGP04.phx.gbl...[color=green]
>>
>> "houstonmat" <houstonmat@discussions.microsoft.com> wrote in message
>> news:A9C3DD70-221B-411D-A61E-1DC3F1379A7B@microsoft.com...[color=darkred]
>>> On two different Vista Home Premium laptops, two different architectures
>>> and
>>> laptop models and three different wireless routers I have experienced
>>> the
>>> following issue. After about 15 minutes of being connected, my wireless
>>> connection drops the Internet connection and becomes 'local access
>>> only.'
>>> Local access is true, because I can stream from my 360, but the laptop
>>> cannot
>>> access the internet. Just renewing the IP isn't enough, I have to
>>> completely
>>> reset the adapter. A cursory search of the internet shows that this
>>> happens
>>> on just about every imaginable platform and hardware configuration out
>>> there.
>>>
>>> What gives, Microsoft? When will this be patched?? I bought this laptop
>>> for
>>> my wife so that she *wouldn't* be calling me all day at work to help
>>> her, yet
>>> the support calls are through the roof!!
>>>[/color]
>>
>> Have you tried running the Vista wireless diagnostic tool to see if it
>> reveals a possible cause?
>>
>> [url]http://technet2.microsoft.com/WindowsVista/en/library/3ed3d027-5ae8-4cb0-ade5-0a7c446cd4f71033.mspx?mfr=true[/url][/color]
> I had exactly the same problem recently, other than it would not even
> start to access the Internet.[/color]

That's because the computer and its wireless NIC never got a DHCP IP from
the router that was going to let it access the Internet. In addition to
that, the machine cannot even access the router's admin pages either using
the router's device IP, because it was not using an IP on the router.
[color=blue]
> However I could connect to any other computer on the LAN. The diagnostic
> tool only gave me a message that a firewall policy could be the problem.
> I only use the Windows Vista firewall.[/color]

That is correct. The computer couldn't get a DHCP IP from the router and
timed out. When the computer couldn't get an IP from the DHCP server on the
router, the O/S assigned a default IP to the NIC of 169.xxx.xxx.xxx. The 169
IP will allow the computer to access other machines on the LAN. But the 169
IP will not allow the computer to access the Internet nor will the IP allow
the computer to access the router's admin page, because the computer is not
using an IP on the router.
[color=blue]
> I eventually just did a "system restore" back a couple of days and now
> the Internet works again.[/color]

I am glad it worked out for you.

Well after 2 solid days of troubleshooting this one, I'm prepared to chalk it
up to a bug. I don't know for sure whether I blame Microsoft, HP or Intel,
but there's no doubt it's a bug...and a well-documented one judging from the
number of search results I get.

I have upgraded both routers' firmware to the latest versions, run all
Windows, HP and Intel updates (wireless NIC is Intel), run all Intel
diagnostics with positive results, made the DHCP broadcast flag changes in
the registry ([url]http://support.microsoft.com/default.aspx/kb/928233/en-us)[/url],
tried AutoConfig on and off
([url]http://www.neowin.net/forum/lofiversion/index.php/t540668.html)[/url], used a
static IP address (worked the best but not permanent), tested every
individual broadcast channel on my router
([url]http://forums.linksys.com/linksys/board/message?board.id=Wireless_Adapters&message.id=4868&query.id=24271#M4868)[/url],
performed a system restore from the D drive image HP ships (back to factory
settings), created another user profile, turned power settings to high
performance, unplugged EVERYTHING in my house that uses a wireless signal
except for the router and laptop (even with draft N I still had the
problem)...that's all I can remember doing, but I'm sure it's not everything
I tried. The lovely thing about it all is that my XP laptop was on during
various times throughout this ordeal and NEVER NEVER NEVER had a problem
connecting and staying connected or accessing the public Internet.

Today I'll be making a trip to Fry's to get my money back. If anyone can
suggest a place where I can find a laptop with XP MCE and 128-256 MB of
dedicated video memory, I'd appreciate it. Or if someone from MS will
acknowledge this bug and let me know when it will be fixed, I'll hang onto
this laptop a little longer. You have 1 hour... :)

All I can tell you is that if you're reading this post because you have the
same issue, RUN back to the store where you bought it and return or exchange
it. You will not be able to fix it, and will be left resetting your wireless
adapter every 10 minutes.

I posted my "final" findings, but it put it onto the second page, so I'm
going to re-post to get it up front. Here goes...

Well after 2 solid days of troubleshooting this one, I'm prepared to chalk
it up to a bug. I don't know for sure whether I blame Microsoft, HP or Intel,
but there's no doubt it's a bug...and a well-documented one judging from the
number of search results I get.

I have upgraded both routers' firmware to the latest versions, run all
Windows, HP and Intel updates (wireless NIC is Intel), run all Intel
diagnostics with positive results, made the DHCP broadcast flag changes in
the registry ([url]http://support.microsoft.com/default.aspx/kb/928233/en-us)[/url],
tried AutoConfig on and off
([url]http://www.neowin.net/forum/lofiversion/index.php/t540668.html)[/url], used a
static IP address (worked the best but not permanent), tested every
individual broadcast channel on my router
([url]http://forums.linksys.com/linksys/board/message?board.id=Wireless_Adapters&message.id=4868&query.id=24271#M4868)[/url],
performed a system restore from the D drive image HP ships (back to factory
settings), created another user profile, turned power settings to high
performance, unplugged EVERYTHING in my house that uses a wireless signal
except for the router and laptop (even with draft N I still had the
problem)...that's all I can remember doing, but I'm sure it's not everything
I tried. The lovely thing about it all is that my XP laptop was on during
various times throughout this ordeal and NEVER NEVER NEVER had a problem
connecting and staying connected or accessing the public Internet.

Today I'll be making a trip to Fry's to get my money back. If anyone can
suggest a place where I can find a laptop with XP MCE and 128-256 MB of
dedicated video memory, I'd appreciate it. Or if someone from MS will
acknowledge this bug and let me know when it will be fixed, I'll hang onto
this laptop a little longer. You have 1 hour... :)

All I can tell you is that if you're reading this post because you have the
same issue, RUN back to the store where you bought it and return or exchange
it. You will not be able to fix it, and will be left resetting your wireless
adapter every 10 minutes.

Have you contacted HP Support yet?


"houstonmat" <houstonmat@discussions.microsoft.com> wrote in message
news:05BCF343-F6BF-4F1D-A798-827C7CDA2CBA@microsoft.com...[color=blue]
> Well after 2 solid days of troubleshooting this one, I'm prepared to chalk
> it
> up to a bug. I don't know for sure whether I blame Microsoft, HP or Intel,
> but there's no doubt it's a bug...and a well-documented one judging from
> the
> number of search results I get.
>
> I have upgraded both routers' firmware to the latest versions, run all
> Windows, HP and Intel updates (wireless NIC is Intel), run all Intel
> diagnostics with positive results, made the DHCP broadcast flag changes in
> the registry ([url]http://support.microsoft.com/default.aspx/kb/928233/en-us)[/url],
> tried AutoConfig on and off
> ([url]http://www.neowin.net/forum/lofiversion/index.php/t540668.html)[/url], used a
> static IP address (worked the best but not permanent), tested every
> individual broadcast channel on my router
> ([url]http://forums.linksys.com/linksys/board/message?board.id=Wireless_Adapters&message.id=4868&query.id=24271#M4868)[/url],
> performed a system restore from the D drive image HP ships (back to
> factory
> settings), created another user profile, turned power settings to high
> performance, unplugged EVERYTHING in my house that uses a wireless signal
> except for the router and laptop (even with draft N I still had the
> problem)...that's all I can remember doing, but I'm sure it's not
> everything
> I tried. The lovely thing about it all is that my XP laptop was on during
> various times throughout this ordeal and NEVER NEVER NEVER had a problem
> connecting and staying connected or accessing the public Internet.
>
> Today I'll be making a trip to Fry's to get my money back. If anyone can
> suggest a place where I can find a laptop with XP MCE and 128-256 MB of
> dedicated video memory, I'd appreciate it. Or if someone from MS will
> acknowledge this bug and let me know when it will be fixed, I'll hang onto
> this laptop a little longer. You have 1 hour... :)
>
> All I can tell you is that if you're reading this post because you have
> the
> same issue, RUN back to the store where you bought it and return or
> exchange
> it. You will not be able to fix it, and will be left resetting your
> wireless
> adapter every 10 minutes.[/color]

--


Mike Hall
MS MVP Windows Shell/User
[url]http://msmvps.com/blogs/mikehall/[/url]

Yes. Spent over an hour on the phone with them. Their final suggestion was to
perform the system restore...which didn't fix the problem.

"Mike Hall - MVP" wrote:
[color=blue]
> Have you contacted HP Support yet?
>
>
> "houstonmat" <houstonmat@discussions.microsoft.com> wrote in message
> news:05BCF343-F6BF-4F1D-A798-827C7CDA2CBA@microsoft.com...[color=green]
> > Well after 2 solid days of troubleshooting this one, I'm prepared to chalk
> > it
> > up to a bug. I don't know for sure whether I blame Microsoft, HP or Intel,
> > but there's no doubt it's a bug...and a well-documented one judging from
> > the
> > number of search results I get.
> >
> > I have upgraded both routers' firmware to the latest versions, run all
> > Windows, HP and Intel updates (wireless NIC is Intel), run all Intel
> > diagnostics with positive results, made the DHCP broadcast flag changes in
> > the registry ([url]http://support.microsoft.com/default.aspx/kb/928233/en-us)[/url],
> > tried AutoConfig on and off
> > ([url]http://www.neowin.net/forum/lofiversion/index.php/t540668.html)[/url], used a
> > static IP address (worked the best but not permanent), tested every
> > individual broadcast channel on my router
> > ([url]http://forums.linksys.com/linksys/board/message?board.id=Wireless_Adapters&message.id=4868&query.id=24271#M4868)[/url],
> > performed a system restore from the D drive image HP ships (back to
> > factory
> > settings), created another user profile, turned power settings to high
> > performance, unplugged EVERYTHING in my house that uses a wireless signal
> > except for the router and laptop (even with draft N I still had the
> > problem)...that's all I can remember doing, but I'm sure it's not
> > everything
> > I tried. The lovely thing about it all is that my XP laptop was on during
> > various times throughout this ordeal and NEVER NEVER NEVER had a problem
> > connecting and staying connected or accessing the public Internet.
> >
> > Today I'll be making a trip to Fry's to get my money back. If anyone can
> > suggest a place where I can find a laptop with XP MCE and 128-256 MB of
> > dedicated video memory, I'd appreciate it. Or if someone from MS will
> > acknowledge this bug and let me know when it will be fixed, I'll hang onto
> > this laptop a little longer. You have 1 hour... :)
> >
> > All I can tell you is that if you're reading this post because you have
> > the
> > same issue, RUN back to the store where you bought it and return or
> > exchange
> > it. You will not be able to fix it, and will be left resetting your
> > wireless
> > adapter every 10 minutes.[/color]
>
> --
>
>
> Mike Hall
> MS MVP Windows Shell/User
> [url]http://msmvps.com/blogs/mikehall/[/url]
>
>
>
>[/color]

"Mr. Arnold" <MR. [email]Arnold@Arnold.com[/email]> wrote in message
news:%23gLQLtZ0HHA.1100@TK2MSFTNGP06.phx.gbl...[color=blue]
>
> "Richard in AZ" <me@mailinator.com> wrote in message
> news:ez%23QbfZ0HHA.5884@TK2MSFTNGP02.phx.gbl...[color=green]
>>
>> "Mr. Arnold" <MR. [email]Arnold@Arnold.com[/email]> wrote in message
>> news:%23jk70$X0HHA.748@TK2MSFTNGP04.phx.gbl...[color=darkred]
>>>
>>> "houstonmat" <houstonmat@discussions.microsoft.com> wrote in message
>>> news:A9C3DD70-221B-411D-A61E-1DC3F1379A7B@microsoft.com...
>>>> On two different Vista Home Premium laptops, two different architectures and
>>>> laptop models and three different wireless routers I have experienced the
>>>> following issue. After about 15 minutes of being connected, my wireless
>>>> connection drops the Internet connection and becomes 'local access only.'
>>>> Local access is true, because I can stream from my 360, but the laptop cannot
>>>> access the internet. Just renewing the IP isn't enough, I have to completely
>>>> reset the adapter. A cursory search of the internet shows that this happens
>>>> on just about every imaginable platform and hardware configuration out there.
>>>>
>>>> What gives, Microsoft? When will this be patched?? I bought this laptop for
>>>> my wife so that she *wouldn't* be calling me all day at work to help her, yet
>>>> the support calls are through the roof!!
>>>>
>>>
>>> Have you tried running the Vista wireless diagnostic tool to see if it reveals a possible cause?
>>>
>>> [url]http://technet2.microsoft.com/WindowsVista/en/library/3ed3d027-5ae8-4cb0-ade5-0a7c446cd4f71033.mspx?mfr=true[/url][/color]
>> I had exactly the same problem recently, other than it would not even start to access the
>> Internet.[/color]
>
> That's because the computer and its wireless NIC never got a DHCP IP from the router that was
> going to let it access the Internet. In addition to that, the machine cannot even access the
> router's admin pages either using the router's device IP, because it was not using an IP on the
> router.[/color]

Interesting. This computer has 3 hard drives and a drive switch that allows only one hard drive at
a time to be powered. All other hardware is the same. One hard drive has Windows XP Pro, one has
Vista and the 3rd has a Linux system. Only the Vista machine could not get the Internet
connection. The other two OSs worked just fine.
[color=blue][color=green]
>> However I could connect to any other computer on the LAN. The diagnostic tool only gave me a
>> message that a firewall policy could be the problem. I only use the Windows Vista firewall.[/color]
>
> That is correct. The computer couldn't get a DHCP IP from the router and timed out. When the
> computer couldn't get an IP from the DHCP server on the router, the O/S assigned a default IP to
> the NIC of 169.xxx.xxx.xxx. The 169 IP will allow the computer to access other machines on the
> LAN. But the 169 IP will not allow the computer to access the Internet nor will the IP allow the
> computer to access the router's admin page, because the computer is not using an IP on the router.
>[color=green]
>> I eventually just did a "system restore" back a couple of days and now the Internet works again.[/color]
>
> I am glad it worked out for you.[/color]

[color=blue]
>
> Interesting. This computer has 3 hard drives and a drive switch that
> allows only one hard drive at a time to be powered. All other hardware is
> the same. One hard drive has Windows XP Pro, one has Vista and the 3rd
> has a Linux system. Only the Vista machine could not get the Internet
> connection. The other two OSs worked just fine.[/color]

So? This has nothing to do with it that the machine has 3 HD(s) each running
a different O/S.

The fact remains that while the machine was using the Vista O/S, the O/S
couldn't get an IP from the DHCP server on the router (it was not in contact
with the router for whatever reasons to get a valid IP), and the O/S
assigned the 169 IP to the NIC.

The 169 IP will allow the machine to access other machines on the LAN, but
the machine cannot access the Internet, because the 169 IP was not an IP
that was an IP on the router assigned by the router's DHCP server. The IP
will not stop the one machine from accessing other machines attached to the
router (the LAN).

[url]http://www.pctechbytes.com/computer/article-8.html[/url]

And if for whatever reasons a machine is obtaining an IP from a DHCP server
will start dropping the connection, it doesn't matter where the DHCP server
is located it can be on the router, FW appliance, another computer acting as
the DHCP server on the LAN or the ISP's DHCP server for a computer that has
a direct connection to the modem and is a direct connection to the ISP's
network, then the 169 IP is going to be assigned to the NIC, if the
connection is dropped. It doesn't matter what O/S is being used as the 169
IP is an IANA standard for this condition.

I suggest you look up the 169 IP and see how that machine could access other
machines on the LAN, but the machine that has the 169 IP cannot access the
Internet. That's the only condition you were talking about it could be.

houstonmat wrote:[color=blue]
> Well after 2 solid days of troubleshooting this one, I'm prepared to
> chalk it up to a bug. I don't know for sure whether I blame
> Microsoft, HP or Intel, but there's no doubt it's a bug...and a
> well-documented one judging from the number of search results I get.[/color]

Judging from another post someone made in this thread about the same
thing happening on a computer triple booting between XP Pro, Vista, and
Linux, and only Vista exhibits the problem. So it looks like YAVB ( Yet
Another Vista Bug [TM] )

I still think such a bug is hardly excusable considering this was
working fine in previous operating systems.

-saran

"Saran" <none@nospam> wrote in message
news:uniNaq70HHA.4344@TK2MSFTNGP03.phx.gbl...[color=blue]
> houstonmat wrote:[color=green]
>> Well after 2 solid days of troubleshooting this one, I'm prepared to
>> chalk it up to a bug. I don't know for sure whether I blame
>> Microsoft, HP or Intel, but there's no doubt it's a bug...and a
>> well-documented one judging from the number of search results I get.[/color]
>
> Judging from another post someone made in this thread about the same thing
> happening on a computer triple booting between XP Pro, Vista, and Linux,
> and only Vista exhibits the problem. So it looks like YAVB ( Yet Another
> Vista Bug [TM] )
>
> I still think such a bug is hardly excusable considering this was working
> fine in previous operating systems.[/color]

I guess you missed that part when the poster said he did get it to work with
Vista.

Mr. Arnold wrote:[color=blue]
> "Saran" <none@nospam> wrote in message
> news:uniNaq70HHA.4344@TK2MSFTNGP03.phx.gbl...[color=green]
>> houstonmat wrote:[color=darkred]
>>> Well after 2 solid days of troubleshooting this one, I'm prepared to
>>> chalk it up to a bug. I don't know for sure whether I blame
>>> Microsoft, HP or Intel, but there's no doubt it's a bug...and a
>>> well-documented one judging from the number of search results I get.[/color]
>>
>> Judging from another post someone made in this thread about the same
>> thing happening on a computer triple booting between XP Pro, Vista,
>> and Linux, and only Vista exhibits the problem. So it looks like
>> YAVB ( Yet Another Vista Bug [TM] )
>>
>> I still think such a bug is hardly excusable considering this was
>> working fine in previous operating systems.[/color]
>
> I guess you missed that part when the poster said he did get it to
> work with Vista.[/color]

I haven't been able to find such a follow up. If it's there please
provide a link.

and even if he says, I find it utterly inexable one should have ot go
thorugh so many hoops to get it works, when it worked perfectly in XP
SP2.

-saran

I tried everything, I bought a new adapter, new router, new firmware installed, latest patches and nothing worked. So I formatted the PC and installed XP. works like a charm and has not disconnected not even once.
Guys stop wasting your time. Get rid of vista. install XP or windows 7. If you are really fed up with MS, I suggest Ubuntu desktop but then again , the wireless driver will be a bit of pain to install.




noaim wrote:

some one else had this issue a few days ago and fixed it by upgrading the
28-Jul-07

some one else had this issue a few days ago and fixed it by upgrading the
routers firmware so I wouldn't limit the fact that it could need the newest
firmware. I'm not guaranteeing that's the fix but its worth a try.




"houstonmat" <houstonmat@discussions.microsoft.com> wrote in message
news:46619423-2AAD-43F0-BBDA-DA9E2C8BD2A1@microsoft.com...

Previous Posts In This Thread:

On Friday, July 27, 2007 2:58 PM
Saran wrote:

Re: Wireless Disconnects - a Vista Bug
houstonmat wrote:

Simple answer: Vista is broken

I've been using Wireless on XP SP2 for 5 years now wit no problems what
so ever. There is absolutely no excuse for such a shoddy translation of
it to Vista, seeing as it's supposed to be bet tech and all, and coupled
with the fact that this was fixed in XP with SP2, it's absolutely
bewildering that they managed to break it. It's one in a very long list
of broken components in Vista. Sigh.

-saran

On Friday, July 27, 2007 4:25 PM
John wrote:

See if there might be a correlation between the specific wireless NIC adapters
See if there might be a correlation between the specific wireless NIC
adapters in the computers and the router. Many times it's problematic to mix
and match hardware. I know I have changed wireless NICs and been rid of
connection problems. Explore router firmware and NIC firmware. Then drivers.
The drivers for XP were older, most likely, than the ones for Vista now. I'm
not supporting Vista since I find it's an OS that tries to do too much (OS,
firewall, malware and more) rather than focusing on being an OS first and
letting 3rd parties fill the other needs as has happened in XP (pre-SP2) and
Win2K. Good luck.


"houstonmat" <houstonmat@discussions.microsoft.com> wrote in message
news:A9C3DD70-221B-411D-A61E-1DC3F1379A7B@microsoft.com...

On Friday, July 27, 2007 6:06 PM
C wrote:

Houstonmat,I had the same problem with my new computer running Vista Home
Houstonmat,

I had the same problem with my new computer running Vista Home Premium and
then Ultimate. I made several calls to Dell and Microsoft trying to
understand the problem.

Who is the vendor of your laptops? Is it Dell. If so, click on All Programs
and go to Dell Wirelss. Uncheck the box that says "Let Dell manage your
wireless connections". This will then let Windows manage the connection.

However, I still had some problems. After a bit more researching I was
advised to update the driver for my wireless card. This permanently solved
the problem for me. It may or may not work for you but the thing I discovered
was that it was not the fault of my Vista operating system.

Have a nice day.

C.B.

On Friday, July 27, 2007 6:48 PM
MickMurph wrote:

RE: Wireless Disconnects - a Vista Bug
Is it a Netgear Router?

"CB" wrote:

On Saturday, July 28, 2007 12:26 PM
houstonma wrote:

No, it's currently a Linksys WRTSL54GS but I've also tried two D-link routers,
No, it's currently a Linksys WRTSL54GS but I've also tried two D-link
routers, one a DI-524 and the other a new draft N (returned it for the
Linksys). I actually still have the DI-524 but I've unplugged it in favor of
the Linksys. But for testing I swap back and forth.

So far I've tried all suggestions except for searching the NIC
manufacturer's website for new drivers, which I will do today. Static IP
address, disabling IPv6, changing power settings to max performance...etc.
etc. and nothing works yet.

I'll keep you posted.

On Saturday, July 28, 2007 1:09 PM
noaim wrote:

some one else had this issue a few days ago and fixed it by upgrading the
some one else had this issue a few days ago and fixed it by upgrading the
routers firmware so I wouldn't limit the fact that it could need the newest
firmware. I'm not guaranteeing that's the fix but its worth a try.




"houstonmat" <houstonmat@discussions.microsoft.com> wrote in message
news:46619423-2AAD-43F0-BBDA-DA9E2C8BD2A1@microsoft.com...

On Saturday, July 28, 2007 9:28 PM
Mr. Arnold wrote:

Re: Wireless Disconnects - a Vista Bug
"houstonmat" <houstonmat@discussions.microsoft.com> wrote in message
news:A9C3DD70-221B-411D-A61E-1DC3F1379A7B@microsoft.com...

Have you tried running the Vista wireless diagnostic tool to see if it
reveals a possible cause?

[url]http://technet2.microsoft.com/WindowsVista/en/library/3ed3d027-5ae8-4cb0-ade5-0a7c446cd4f71033.mspx?mfr=true[/url]

EggHeadCafe - Software Developer Portal of Choice
Build A C# DNS MX Mail Record Query Class
[url]http://www.eggheadcafe.com/tutorials/aspnet/2e13787b-5856-4020-889e-ea76e8506a27/build-a-c-dns-mx-mail-re.aspx[/url]