Active Directory 0x51 Error
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 suitability of server an active directory domain could not be contacted '
Active Directory Error 0x51 Occurred When Trying To Check Server
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 org level, as well as using the active directory error 0x8000ffff -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
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 an active directory error 0x51 exchange 2007 Job Ways to Get Help Expand Search Submit Close Search Login Join Today
Active Directory Error 0x51 Ldap Server Unavailable
Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Exchange 2010
Active Directory Fehler 0x51
- 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,285 Views Last 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 Modified: 2014-04-14 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 https://www.experts-exchange.com/questions/27726429/Exchange-2010-Active-Directory-error-0x51-LDAP.html 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 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
Domain controller / LDAP Server has SSL ?The following URL has a nice write up about the Microsoft Tool called LDP.exehttp://www.computerperformance.co.uk/w2k3/utilities/ldp.htmYou can download ldp.zip directly from here : http://www.computerperformance.co.uk/ScriptsGuy/ldp.zipor copy from your Windows 2000 / 2003 Support Tools CD.Microsoft says :Verifying an LDAPS connectionAfter a certificate is installed, follow these steps to verify that LDAPS is enabled:1. Start the Active Directory Administration Tool (Ldp.exe).2. On the Connection menu, click Connect.3. Type the name of the domain controller to which you want to connect.a. You must use a proper DNS name for the SSL test to work.4. Type 636 as the port number and check the SSL box5. Click OK.RootDSE information should print in the right pane, indicating a successful connection.If you get an error saying, "Cannot open connection," LDP cannot establish a secure connection to the directory server. In this case, it's very likely that the server is not configured properly for LDAP over SSL. Verify the server name/IP address and port number. You can also use the Portqry tool to verify that the directory server is listening on the correct port.The following LDP output (for server name dc01) indicates that the connection failed because the certificate used in the SSL connection cannot be trusted:ld = ldap_sslinit("dc01", 636, 1);Error <0x0> = ldap_set_option(hLdap,LDAP_OPT_PROTOCOL_VERSION, LDAP_VERSION3);Error <0x51> = ldap_connect(hLdap, NULL);Server error: {empty}Error <0x51>: Fail to connect to dc01.You can test connecting non ssl communication by unchecking the SSL box and changing the port to 389The same ldp.exe program can also be used to test the connection to the Global Catalog.Follow the same steps as before, but change the ports.The Non SSL port for the global catalog is 3268The SSL port for the global catalog is 3269Another tool that is good for checking the SSL cert can be downloaded from here : http://swdl.stone-ware.com/support/techdocs/kb/s1189/ViewDirCert.zip Help Desk Software by Zoho Support Loading...