Ive gotten 7 different reports over the past month of guests whose laptops can see and try to connect to my MT APs but never fully connect or work (they get the limited connectivity messages in windows)
BUT they ALL report being able to choose and connect to (and surf) onto a rogue linksys AP that a condo next door has.
we have 20 MT APs at this install- ppl are seeing this on all floors,all mts
the log messages we get when this occurs is the same, every where:
mac addy@wlanX connected
then about 20 sec later:
mac addy@wlanX disconnected, got disassoc: unspecified.
most of the time they will connect log enough to pull an IP addy from our DHCP server, but like i said the got disassoc: unspecified kills it.
At first it thougth this was just a few isolated issues with peoples buggy laptops, but we are seeing WAY to much of this recently with too many reports of the same ppl being able to connect to the 3 or 4 rogue linksys APs that spill over in some of our area.
2.9.3 or 2.9.30 ?
And is the laptop Centrino with Intel wi-fi card. There are lot of complaining about them, just install them latest driver from the Intels site.
The complaining is Intel wi-fi vs. Athers AP with recently new drivers and capabilities, and there is proof that the problem is with intel compatibilty, soo they released new driver.
