An Active Directory Error 0x51 Occurred
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 occurred when trying to check the
An Active Directory Error 0x51 Occurred When Trying To Check Server
suitability of server '
Active Directory Error 0x51 Occurred Exchange
to vote This issue is driving us nuts - there are no issues with Domain Controllers or AD in this environment. The server it is citing in the error has been active directory error 0x51 ldap server unavailable 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 help but expect these 2 issues are related? I tried hard coding the Configuration Domain Controller at the active directory response the ldap server is unavailable exchange 2013 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. Recently we ran into a
Error Active Directory Response The Ldap Server Is Unavailable
similar problem that drove us nuts. We had just recently demoted one kb2019500 of our old domain controllers. For a few days everything worked fine. But, just recently our Exchange
An Active Directory Error 0x52 Occurred When Trying To Check Server
Server 2010 started throwing up error 0x51 while pointing to the demoted domain controller. The whole database would be locked up and mostly a restart would make the problem 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 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 - Remote Management Date: DATE Event ID: 4 Task Category: General Level: Error Keywords: http://email-converter-tools.blogspot.com/2013/02/a-permanent-resolve-for-microsoft.html 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 Console. But the issue still lingered on and there was no other way but to opt for a third party Exchange Server Recovery tool. Stellar Phoenix Mailbox Exchange Ser
Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get https://www.experts-exchange.com/questions/27726429/Exchange-2010-Active-Directory-error-0x51-LDAP.html Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers https://support.software.dell.com/kb/150374 Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Exchange 2010 - Active Directory error 0x51 LDAP Want to Advertise Here? Solved Exchange 2010 - Active Directory error 0x51 LDAP Posted on 2012-05-21 Exchange Active Directory 1 Verified Solution 7 Comments 4,287 Views Last Modified: 2014-04-14 Hi all. We've got two domain controllers. active directory 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] active directory error 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 0 Question by:Opusretis Facebook Twitter LinkedIn Google Best Solution byOpusretis 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. Go to Solution 7 Comments LVL 13 Overall: Level 13 Active Directory 7 Exchange 4 Message Active 7 days ago Expert Comment by:Kini Pradeep2012-05-22 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 ? 0 Message Author Comment by:Opusretis2012-05-22 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 0 LVL 13 Overall: Level 13 Active Directory 7 Exchange 4 Message Active 7 days ago Expert
SonicWALL User Sorry, we are having issues processing your request. If you own the SonicWALL product requested please confirm that you have registered your product at My SonicWALL . If you have already registered your product then please contact Customer Service directly for further assistance at customerservice@software.dell.com. Continue Search Sign In Sign In Create Support Account Products ActiveRoles Boomi Change Auditor Foglight Identity Manager KACE Migration Manager Rapid Recovery Recovery Manager SharePlex SonicWALL Spotlight Statistica Toad View all Products Solutions Application & Data Integration Big Data Analytics Business Intelligence Cloud Management Data Protection Overview Backup and Recovery Deduplication and Compression Database Development & Management Database Replication & Backup Endpoint Management Mobile Workforce Management Overview Desktop Virtualization Enterprise Mobility Management Endpoint Security Network Security Secure Remote Access Performance Monitoring Security Overview Email Security Endpoint Security Identity & Access Management Network Security Secure Remote Access Virtualization Management Microsoft Platform Management View all Solutions Solutions by Platform Active Directory Exchange Google GroupWise & NDS Hadoop Hyper-V Lotus Notes Skype for Business/Lync Office 365 Oracle SharePoint SQL Server VMware Trials Buy Support By Product Line Enterprise Reporter Foglight KACE Migration Manager Migrator NetVault One Identity Quick Connect Performance Analysis Recovery Manager Shareplex SonicWALL Spotlight SQL Navigator Toad All Products Contact Support Download Software Knowledge Base My Account My Products My Service Requests My Licenses My Groups My Profile Policies & Procedures Professional Services Technical Documentation Training & Certification User Forums Video Tutorials Support Home Communities Partners × Email Share your favorite Support content with a friend. Email To Email From Subject Information from Dell Software Support Message You might be interested in the following information For more information regarding support on your Dell Software Product, please visit www.software.dell.com/support Print Email My Downloads () Support Knowledge Base One Identity Quick Connect Exchange Resource Forests Error when creating Linked Mailbox with One Identity Quick Connect Exchange Resource Forests (150374) × Return Feedback submitted. Was this article helpful? [Select Rating] Title Error when creating Linked Mailbox with One Identity Quick Connect Exchange Resource Forests De