IDPInc
asked on
DC name not resolving in Recipient Update Service
I had been getting the errors 8026 and 8062, "
LDAP Bind was unsuccessful on directory dc.domain.com for distinguished name ''. Directory returned error:[0x51] Server Down. DC=,DC=com
And I checked out all of the other suggestions. When i went into the RUS to select a DC, it won't allow me to select what I consider to be my Primary DC. It resolves the other one, but not this one. I successfully pinged the DC, same with nslookup. I had been having DNS issues, but what can I do to resolve this?
LDAP Bind was unsuccessful on directory dc.domain.com for distinguished name ''. Directory returned error:[0x51] Server Down. DC=,DC=com
And I checked out all of the other suggestions. When i went into the RUS to select a DC, it won't allow me to select what I consider to be my Primary DC. It resolves the other one, but not this one. I successfully pinged the DC, same with nslookup. I had been having DNS issues, but what can I do to resolve this?
ASKER
Yes, both DC's are GC's
ASKER
Clarification. We have two RUS's the Enterprise COnfiguration, and then the domain related one in the second position. The Enterprise one seems to resolve just fine, but the second one does not. These were created before me. Are two of them necessary? Again I don't want to break more than I fix.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Single domain environment.
Simon.