After updating from 5.1 to 5.5 we had issues logging in with ldap from the web. Clients would connect and work. Issue was resolved after looking at the ad connector. It had the fully qualified name in there and was resolved by changing to the short AD name. i.e "windows.local" went to "windows".
After that everything worked.
Posting for others with this issue
Free Guide: Managing storage for virtual environments
Complete a brief survey to get a complimentary 70-page whitepaper featuring the best methods and solutions for your virtual environment, as well as hypervisor-specific management advice from TechTarget experts. Don’t miss out on this exclusive content!