200.11.10.5.195 Broken AD Login?

[dan_b]

I recently upgrade to the lastest 200.11.10.5.195, once the AP rebooted I suddenly could no longer login. The login screen would take the username and password, turn it to starts, and then just sit there and flicker. I had to factory reset to get back into the AP. SSH also would just timeout trying to login. Then I tried to re-setup AD login, and it would do the exact same thing. Then after ssh-ing in with local credentials I went to debug mode, and when I run "logs winbind 1" I get the following.

killall: winbindd: no process killed
sh: winbindd: not found

Was winbindd not put into this image?

[syamantakomer]

Hi Dan,

If its a Linux command, it will not work because you are in Ruckus CLI, which is running on top of Linux.

I suggest you to open a case with support and we can look into the issue.

@Ratnadeep check once if you are able to reproduce this in lab.

[CRSR]

Same thing with the latest R850 and 200.12.10.105.129.  I spent hours debugging why TLS would not work (I've setup Unleashed on about 10 other branch offices -- never experienced this before but then again never ran anything past 200.10.xxx).  Downgraded to 200.10.10.5.253 and it worked fine - same exact config/settings.