Community Tip - Stay updated on what is happening on the PTC Community by subscribing to PTC Community Announcements. X
Solved! Go to Solution.
To configure Windchill with Active Directory, you can refer to article https://www.ptc.com/en/support/article/CS29445.
Per the message "javax.naming.CommunicationException: corpldap.mydomain.com:389", make sure your Windchill machine can connect to your AD server "corpldap.mydomain.com" via the port 389, otherwise, you may try other port like 3268 or check your AD admin.
Are you integrating just the webserver or did you also change your ie settings to connect to the same LDAP?
According to PTC, this is a port issue. Most likely, the port is blocked by firewall.
https://www.ptc.com/en/support/article/CS389562
With Active Directory, use ports 3268 (LDAP) or 3269 (LDAPS). The generic 389 and 636 ports don't provide access to the global catalog, which is commonly needed for Windchill LDAP integrations.
FYI: It is a recommended practice to validate the corporate LDAP connection information provided by IT in an LDAP client like Apache Directory Studio before integrating. It is best to know the server can connect to the LDAP server with the provided information before getting into a Windchill configuration debugging session.
To configure Windchill with Active Directory, you can refer to article https://www.ptc.com/en/support/article/CS29445.
Per the message "javax.naming.CommunicationException: corpldap.mydomain.com:389", make sure your Windchill machine can connect to your AD server "corpldap.mydomain.com" via the port 389, otherwise, you may try other port like 3268 or check your AD admin.