Hi Joel,
I'll keep an eye out for that. When I thought things through a bit
more, I realized that several of the lockups occured with none of the
XP machines on the net. For example, yesterday's first lock up was
1 win2k laptop with Orinoco Gold, a Ti-book, and an iPaq 5455. I
know the two XP laptops were out of the office when some of the
WAP11 lockups occured, so I think the XP issue isn't my root problem,
but might be the original posters and probably was my co-workers
old problem.
thanks for the info!
K^2
> if you have multiple xp machines is one of them try to particpate in an
> adhoc network with the same name? given the way the client
> implementation works it pretty easy to end up associated with an an
> adhoc node unless you explicitly specify otherwise... then the adhoc
> nodes suck the other machines into their non-working netowrk... I have
> observed that behavior in the wild.
>
> joelja
>
>
> On Mon, 24 Feb 2003, Ken Key wrote:
>
>> Hi John,
>>
>> I have had almost identical behavior with 3 different Linksys
>> WAP 11 v2.6 boxes. I snagged a Belkin AP to fill in until my
>> cisco 1100 comes in and it worked fine the past 2 weeks but twice this
>> morning did exactly what the WAP-11's did and what you describe. It's
>> like the Radio gets switched off but the AP itself thinks it's fat,
>> dumb, and happy. I haven't disassembled the boxes to see
>> what chipsets I was dealing with. I got Linksys to take the WAP's
>> back.
>>
>> One of my co-workers had previously had an experience where "XP was
>> killing the APs" at a previous employer and he suspects the 2 XP
>> laptops in the office, but I have not been able to reproduce the
>> problem at will.
>>
>> I'm interested in anything you find out.
>>
>> Regards,
>> Ken Key <[EMAIL PROTECTED]
--
general wireless list, a bawug thing <http://www.bawug.org/>
[un]subscribe: http://lists.bawug.org/mailman/listinfo/wireless
