Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

LDAP in developer instance

amacqueen
Mega Guru

‎06-04-2015 12:50 AM

Just been attempting to set up LDAP in my developer instance and it is failing, got this message:-

ldap://xxx.xxx.xxx.xxx:389/ Connection timed out, failed to connect to server

Verify server address and port are correct and accessible

I seem to recall we had to add a firewall rule to allow SN to talk to our LDAP and I would have thought that existing rule would work however as we are in Europe it may be the developer instances are hosted in the US and I may need an alternative address added.

Any ideas?

TIA

0 Helpfuls
  • 4,052 Views
20 REPLIES 20

Niamul Arifin
Tera Expert

‎02-21-2020 11:59 PM

I understand this thread is very old but still want to update this. I had the same issue tonight when i was trying to connect to my ldap server which is hosted in Azure cloud. It was showing me

 

Connection timed out, failed to connect to server. Verify server address and port are correct and accessible

 

I had to create an inbound rule in the azure platform to make sure all connections are able to reach to the server port 389. In this way, Servicenow dev instance can talk to the Active directory in your Azure VM through 389.

0 Helpfuls