I have a Cisco Aironet 350 access point connected to a Aironet 350 Workgroup Bridge and an generic 802.11b client. The generic client is continuously associating for a few seconds then being disassociated a couple seconds later. I am at a loss to understand how to keep the generic 802.11b client connected. The workgroup bridge has a much weaker signal but maintains it's connection for long periods of time. The Aironet 350 access point's setup seems to be as generic-friendly as possible.
Here is a section of the Cisco Aironet access point association log: 2004/04/13 11:30:47 Info Disassociating [192.168.123.25]000625250117, reason "Not Associated" 2004/04/13 11:30:37 Info Station [192.168.123.25]000625250117 Associated 2004/04/13 11:30:37 Info Station [192.168.123.25]000625250117 Authenticated 2004/04/13 11:30:32 Info Disassociating [192.168.123.25]000625250117, reason "Not Associated" 2004/04/13 11:30:07 Info Station [192.168.123.25]000625250117 Associated 2004/04/13 11:30:07 Info Station [192.168.123.25]000625250117 Authenticated 2004/04/13 11:30:02 Info Disassociating [192.168.123.25]000625250117, reason "Not Associated" 2004/04/13 11:29:52 Info Station [192.168.123.25]000625250117 Associated 2004/04/13 11:29:52 Info Station [192.168.123.25]000625250117 Authenticated 2004/04/13 11:29:47 Info Disassociating [192.168.123.25]000625250117, reason "Not Associated" Any suggestions would be greatly appreciated. Loren Zemenick _______________________________________________ BAWUG's general wireless chat mailing list [unsubscribe] http://lists.bawug.org/mailman/listinfo/wireless
