Your AD could be configured to only accept ldaps/SSL connections, which would be port 636. Also, you might check the firewall policy on your AD server to make sure it would accept connections from your CAS server's IP.
On Thu, Jan 17, 2013 at 11:45 AM, Marvin Addison <[email protected]>wrote: > > Thoughts on how to diagnose the issue? > > I would recommend tcpdump on the CAS server to troubleshoot a purely > networking problem. If you see a successful three-way handshake, then > you should look at SSL/TLS issues by performing a Java SSL trace [1]. > With one or both of those you should have some evidence to present to > your networking or AD admins. > > M > > [1] > https://wiki.jasig.org/display/CASUM/SSL+Troubleshooting+and+Reference+Guide > , > "When All Else Fails" > > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
