Get a first look at what's coming. The Developer Passport Australia Release Preview kicks off March 12. Dive in! 

LDAPS Connection Error - Unknown Hostname

AnotherNOWDev
Tera Expert

I've been trying to connect with LDAPS without any luck.

 

Our current connection to LDAP works completely fine if we use the IP address with the following format ldap://192.158.1.38:389/

 

After we installed the certificate I'm facing the following error

Error Message ldaps://example01.server.corp:636 Unknown host example01.server.corp
Verify server address and port are correct and accessible

 

The certificate was issued with the following name values:

example01.server.corp
server.corp
SERVER

 

Why am I getting an error when connecting to LDAPS?

 

UPDATE: The following powershell scripts were executed on the MID Server

Test-NetConnection 192.158.1.38 -Port 389 Successful

Test-NetConnection 192.158.1.38 -Port 636 Successful

Test-NetConnection example01.server.corp -Port 636 Error

Test-NetConnection server.corp -Port 636 Error

 

Note: I've changed the ip address and hostname values with samples for disclosure

5 REPLIES 5

Tanushree Maiti
Tera Sage

Hi @AnotherNOWDev 

 

Ensure MID server is up which you have mentioned in the configuration.

 

Run the telnet command to the IP of the LDAP server and specify the port that is being used and test it.

like telnet hostname/ip 389

 

 

Please mark this response as Helpful & Accept it as solution if it assisted you with your question.
Regards
Tanushree Maiti
ServiceNow Technical Architect
Linkedin:

Check these post/ KB article if help you to debug:

https://www.servicenow.com/community/servicenow-ai-platform-forum/port-validation/m-p/1209155

 

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0517267

 

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0657528

 

 

Please mark this response as Helpful & Accept it as solution if it assisted you with your question.
Regards
Tanushree Maiti
ServiceNow Technical Architect
Linkedin:

Regular LDAP connection using port 389 works completely fine. MID Server is up and running with successful ping connection to the AD Server IP.

 

The issue I'm having is with LDAP Secured with port 636.

Hi @AnotherNOWDev 

 

Regarding LDAP with secure port 636 - Refer this post and check

 

LDAPs Integration enable port 636 - ServiceNow Community

 

Please mark this response as Helpful & Accept it as solution if it assisted you with your question.
Regards
Tanushree Maiti
ServiceNow Technical Architect
Linkedin: