Exchange 2010 - Active Directory error 0x51 LDAP

Opusretis
Opusretis used Ask the Experts™
on
Hi all.

We've got two domain controllers. The second is a new one.
First DC ist Windows 2008 Standard, second Windows 2008 R2 Enterprise.
The Exchange Server is 2010 Standard Service Pack 2.

We need the second DC for failover if the first goes down. We tried this szenario (shut down the first domaincontroller) but Exchange is not work on.
We tried to Add the second DC as PreferredServer with the "Set-ADServerSettings" Command in the PowerShell.
[PS] C:\>Set-ADServerSettings -PreferredServer dc2.local
We get the following error message:
An Active Directory error 0x51 occured when trying to check the suitability of server dc2.local
'Active Directory response: The LDAP server is unavailable.
CategoryInfo: NotSpecified: (0:Int32) [Set-ADServerSettings], SuitabilityDirectoryException
FullyQulifiedErrorid: 96AD2D25, Microsoft.Exchange.Management.ADServerSettings.SetADServerSettings
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Kini pradeepDevelopment Manager

Commented:
couple of things first.
once you install the windows 2008 r2 DC, it is advisable to move the FSMO roles from 2008 to R2.
Is the 2008 R2 DC also a Global catalog server ?

In the Exchange console do you see the DC (2008 r2) Listed ?

Author

Commented:
The new one is a global Catalog server.
I did not move the FSMO roles to the new one yet.
Yes the new DC is listed in the exchange console
Kini pradeepDevelopment Manager

Commented:
1. any errors reported in AD (replication, FRS/DFS)
2. what does running nltest /dsgetdc:domainname show. does it list the domain controller with the correct site details.
3. does running dcdiag /v on the new DC report any errors ?
Success in ‘20 With a Profitable Pricing Strategy

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

Author

Commented:
1. I've got errors in DFS from the time where we shut down the first dc to test exchange but that is comprehensible. Further I got one warning today - maybee a short interrupt
Event ID: 5014 - "The DFS Replication service is stopping communication with partner dc1 for replication group domain system volume due to an error. The service will retry the connection periodically"
14 seconds later I've got the information that the connection is successfully reestablished.

2. If I run this command on the exchange, I get the details of the first dc only. The details seems to be correctly (we've got only one site, this is the Default-First-Site-Name).
If I run this command on the new dc I get only the details of the new dc. the details seems to be correctly.

3. Please see attached file
dcdiag.txt
Kini pradeepDevelopment Manager

Commented:
what about DNS, where is the Exchange server  pointing for DNS ?
assuming you are using the AD integrated DNS,
Yes we use the AD integrated DNS - both DC's are DNS Server and they are replicated.

The Exchange is pointing in his networksettings primarly to dc1 and alternatively to dc2.

Author

Commented:
No more answers from Experts

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial