Have you seen this error in your Cisco WLC logs?
Client Association Failure: MACAddress:xx:xx:xx:xx:xx:xx Base Radio MAC:xx:xx:xx:xx:xx:xx Slot: 0 User Name:UNKNOWN IP Addr: unknown Reason:Unknown ReasonCode: 102
There is one link on the internet mentioning this error on the Cisco Support Forums, but I found it might have an alternative solution.
Reboot the AP with the Base Radio MAC that is triggering this error.
I highly doubt this is a silver bullet for this error, but when there’s little other documentation on this error online, I figure I’d share what my fix was.
WARNING: This how-to is brief and technical. If you are unfamiliar with the terms SSH, VI/VIM, and CLI then this tutorial may be difficult for you.
I have always hated that Synology does not have better logging for their backup jobs. Errors include “the backup failed.” Thanks, logs!
It turns out that Synology has these logs, but they are not accessible from the control panel. The logs are in the /var/log/messages file on the server.
- On your NAS -> Control Panel -> Terminal -> Turn on SSH.
- SSH into the NAS using your SSH client of choice. Login with username: root and password of your standard admin password. If you login as “admin” you will not have edit rights.
- Type ‘cd /var/log’ to get to the logs folder
- Type ‘vi messages’ to open the main log file. You can type ‘ls’ or ‘dir’ to see the other log files within the folder. DIR will show you the last edit timestamps, to know what logs are relevant.
If you don’t know how to use vi (aka vim) search for a how-to using your favorite search engine.
If you’ve been trying to setup two Synology NAS devices one being a LDAP Server and another the LDAP Client and you cannot connect with your LDAP account to network shares via SMB, here is your fix.
ON SYNOLOGY LDAP SERVER – Control Panel -> File Services -> Windows File Service/SMB -> Disable “Enable SMB2 and Large MTU”
ON SYNOLOGY LDAP CLIENT – Control Panel -> Directory Service > Enable Windows CIFS support
The only way I could get LDAP between two Synology NAS’s to work with SMB was making sure BOTH of the above are set, not just one or the other.