Hi Uldis
Thanks for the response.
If possible try to reset the wireless interface configuration on the AP and on the non-working station and then configure the settings you only need.
Wont be able to reset AP, production AP, but it does function with other clients, including
Also please upgrade the AP and the Clients to RouterrOS v5.25 or v6.7
Have already upgrade both client and AP to 6.7
Also try to use only AES encryption instead of TKIP.
Using NV2, don't think encryption should be a problem?
Enable the wireless,debug logging on the AP and on the client and check the logs.
Will try this, but i believe there will be a enormous amount of info coming in, but will give it a try.
Disable the access-list entries and check if they are not causing the problem.
Looks like this might be it, perhaps a bug? Default authentication is on, but after disabling the access-list entries, none of the clients could associate with the AP. After enabling them, the associated again.
Took the AP that the SXT Lite does associate with and disabled access-list. Could still associate. This AP had OS 5.23. Upgraded to OS 5.23 to OS 6.7. SXT did not want to associate until i enabled access list entry. Same error in log as other AP's, not allowed. Keep in mind default authentication is enabled. The PTP link, which is also a RB433, did not have a problem and could associate with access list disable even after upgrading to OS 6.7