Skip to main content
Question

AD Bind Failing

  • September 29, 2015
  • 4 replies
  • 29 views

Forum|alt.badge.img+4

When deploying a policy on a 10.10.5 machine through Self-Service using the AD Bind feature in Casper 9.8, I'm getting the following error in the log:

An error occurred binding to Active Directory: dsconfigad: Authentication server could not be contacted. (5200).

The computer binds fine when using the Directory Utility.

4 replies

Forum|alt.badge.img+4
  • Author
  • Contributor
  • 20 replies
  • September 29, 2015

Got it fixed...thought we had to put the DC name at the beginning of the domain.

Works perfectly.


Forum|alt.badge.img+3
  • New Contributor
  • 2 replies
  • October 1, 2015

Can you elaborate on this? What screen did you make the change on? What do you mean by "thought we had to put the DC name at the beginning of the domain."

I'm getting this error too.


Forum|alt.badge.img
  • New Contributor
  • 1 reply
  • August 7, 2017

any update on this? we have the same issue


Steven_Xu
Forum|alt.badge.img+7
  • Contributor
  • 47 replies
  • August 15, 2017

In the Active Directory Domain filed, type the local DNS name of the domain, just like jamf.local or jamf.com