Problem w/ deniedAssociationOnSSID on RFS6000

K KEN LIM 3 years ago
0 0 0

Hi all A customer been using our WS5000; WS5100; AP5131; AP300; CB3000; MC55 and PDT8146. As part of their upgrade exercise to freshen up the instracture, this week they deployed RFS6000 running software version 4.3.4.0-01R + AP650 + AP300 to replace the WS5X00 + AP300. #1. Immediately we get feedback from customer that their users are getting frequent wireless disconnection on their HP iPAQ2600 and PDT8146. They noticed the association to the AP is getting dropped off if not is unable to grab an IP address. The only to get connected is to reset the devices constantly in order to get associated and recognize by the AP. When partner view the log events there was deniedAssociationOnSSID. Description: The station was denied association because the SSID supplied by the MU was too large. Solution: Check your MU software. It appears to be sending a malformed association request. Possible Causes: Interference or a cracking attempt. See attached picture. Anything to do with their SSID "WF03122691195500062W1740SCLV1ATR"? #2. On our MC55 - customer says it take an average of 8 seconds for each scanning of item to have response back to the screen as compare to other stores using the WS5X00/MC55 or AP5131/MC55 where the response time is than 3 seconds. As the customer have been very supportive of Symbol/Motorola Solutions. They have been the longest user of our wireless infrastructure, together with the mobile devices.  We are working with them to upgrade their older wireless access points and there is a pending PO for over 60 units of RFS.  This incident has already undermined their confidence on our products and if we do not react, it may drive them to consider alternative wireless brand.

At this point in time, we do not know what is the issue and some of them could be application related. But it is absolutely important for us to demonstrate our ability to work together with our strategic customer and partner to identify the problem and recommend a solution.

Any suggestion on how to resolve issue #1? Any fix or workaround to share? Thanks ken

CONTACT
Can’t find what you’re looking for?