houstonmat wrote:
> "Ian Betts" wrote:
>> "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!!
>>>
>>> Matt
>>> houstonmat--at--gmail
>> Well for a start it does not happen on mine or any of those I visit
>> to teach. That said I would not jump to blame the Win system but
>> look at ISP prob's and router set up problems first.
>>
>> --
>> Ian
>>
> What OS do you teach on?
>
> I have had nearly a dozen XP laptops connected to my router(s) and
> never an issue whatsoever. Simultaneously I will have my work laptop
> (XP) and this laptop (or its predecessor, both Vista Home Prem)
> connected, and the Vista laptop drops the connection after a few
> minutes while the XP machines have no problems. I have a business
> class connection for which I pay a lot of $$. I know it's not my ISP,
> and I know it's not my router (or the other two routers I tried).
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