An Active Directory Error 0x51
Contents |
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Asked by: Active Directory Error 0x51
An Active Directory Error 0x51 Occurred When Trying To Check Server
occurred when trying to check the suitability of server '
Active Directory Error 0x51 Occurred Exchange
Exchange > Exchange Server 2010 Question 1 Sign in to vote This issue is driving us nuts - there are no issues with Domain Controllers or AD an active directory domain controller for the domain could not be contacted in this environment. The server it is citing in the error has been retired - it was gracefully dcpromo'ed down and removed from the environment. DNS has no record of it, nor is it located anywhere else. We are not able to log into Outlook Web App either with authentication failed errors - and I can't an active directory domain controller cannot be contacted help but expect these 2 issues are related? I tried hard coding the Configuration Domain Controller at the org level, as well as using the -staticdomaincontrollers and -staticglobalcatalogservers with the "Set-ExchangeServer" powershell command - no luck.... System settings of the exchange 2010 servers show they are pointing to the correct DCs - but I still get this error accompanied with long delays in rendering windows in EMC. Extremely frustrating..... I have an issue logged with MS now, but they aren't looking at them until Nov 9. Has anyone seen this issue at all? More info on the OWA config - using Form based auth, and I'm not able to perform a simple test-owaconnectivity -mailboxcredential (get-credential\username) -allowuntrustedcertificate -allowinsecurelogon - please help Thursday, November 05, 2009 4:05 PM Reply | Quote All replies 0 Sign in to vote Hi,Did you try using Get-OwaVirtualDirectory with -DomainController
Error 0x51 Microsoft Exchange administrators get hung up some times when they encounter sudden Exchange Errors.
An Active Directory Error 0x51 Exchange 2010
Recently we ran into a similar problem that drove us nuts. active directory error 0x8000ffff We had just recently demoted one of our old domain controllers. For a few days everything
An Active Directory Error 0x51 Exchange 2007
worked fine. But, just recently our Exchange Server 2010 started throwing up error 0x51 while pointing to the demoted domain controller. The whole database would be locked https://social.technet.microsoft.com/Forums/en-US/5302379e-9c43-49e5-9a20-b935bbe2b875/active-directory-error-0x51-occurred-when-trying-to-check-the-suitability-of-server-servername?forum=exchange2010 up and mostly a restart would make the problem go away. What actually happens is that the Exchange Management Console tries to connect to the non-existent DC which was a part of the network sometime back. This would throw up an error message similar to this: Log Name: Application Source: MSExchange Configuration Cmdlet http://email-converter-tools.blogspot.com/2013/02/a-permanent-resolve-for-microsoft.html - Remote Management Date: DATE Event ID: 4 Task Category: General Level: Error Keywords: Classic User: N/A Computer: COMPUTER NAME Description: Error: Microsoft.Exchange.Data.Directory.SuitabilityDirectoryException: An Active Directory error 0x51 occurred when trying to check the suitability of server ‘SERVER NAME'. Error: ‘Active directory response: The LDAP server is unavailable.' What we found online was that the aforestated error is a result of Exchange Management Console trying to connect to an old domain controller that is no longer available. To point to the new domain controller we had to follow these steps: • Open Exchange Management Console • Right click on Organization Configuration • Click Modify Configuration Domain Controller • Check Use Default Domain Controller This should have resolved the issue. However, we were able to execute the same steps successfully but the problem persisted. We tried another solution that was to delete the Exchange Management Console file from the following location: C:\users\\AppData\Roaming\Microsoft\MMC\Exchange Management Console Close and restart Exchange Management Cons