Why would our LDAP settings work for 1 environment but not the other?

We have a test environment for Jira and a Production environment. We tested the ability to add our newly acquired Active Directory (LDAP), and it connected in the test environment. Now we are trying to move this over to our Prod environment and we get the error below.

Test basic connection : Failed

grcpdc1.grnriver.local:389; nested exception is javax.naming.CommunicationException: grcpdc1.grnriver.local:389 [Root exception is java.net.UnknownHostException: grcpdc1.grnriver.local]

1 answer

0 vote

Your network is not resolving the name correctly.

On the failing server, it can't resolve grcpdc1.grnriver.local to any server. Check DNS, and the local hosts file on the server to see if there's anything odd on there.

At the very least, just try "nslookup grcpdc1.grnriver.local" - it might tell you a bit more about why it's not able to locate the server.

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Posted Tuesday in Uncategorized

Friday fun: how many celebrates Midsummer holiday or is this a Swedish tradition only?

Any other country that celebrates Midsummer holiday (this friday 22 June)?  

44 views 3 1
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you