Ldap Error 0x51 Server Down Ldap_open
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) Home20132010Other VersionsLibraryForumsGallery Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: LDAP Server is down Windows Server > ldap error 81 server down Directory Services Question 0 Sign in to vote Hi, I have ldap error 81 0x51 server down established a trust relationship between two domain and I thought it was fine because I can see the users from each one of the domains but I needed to run this command: setspn -l firsdomain\admin from the seconddomain and I get the error: Ldap Error (0x51 -- Server down): ldap_open Can anybody help me? Which tests I can do to fix the problem? Thanks in advance. Regards. Thursday, January 30, 2014 3:34 PM Reply | Quote Answers 0 Sign in to vote Looks like your DNS lookups are failing. Without being able to resolve the _LDAP records for
for 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 Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Unable to set SPN for the FIM Service in Windows Server 2008 R2 Want to Advertise Here? Solved Unable https://social.technet.microsoft.com/Forums/office/en-US/45c65348-97d4-4733-9e0d-91ce61e61544/ldap-server-is-down?forum=winserverDS to set SPN for the FIM Service in Windows Server 2008 R2 Posted on 2012-01-06 MS Forefront-ISA Windows Server 2008 Active Directory 1 Verified Solution 2 Comments 1,278 Views Last Modified: 2014-02-06 Hi, I am trying to set up a Service Principal Name (SPN) for the FIMservice with a domain account on Windows server 2008. The name of https://www.experts-exchange.com/questions/27524437/Unable-to-set-SPN-for-the-FIM-Service-in-Windows-Server-2008-R2.html the service and account is FIMService My command is as below setspn -S FIMService/localhost CORP\FIMService The output of the command is : Ldap Error <0X51 -- Server Down > : ldap_connecct Failed to retrieve DN for domain "" : 0x00000051 Warning: No valid targets specified, reverting to current domain FindDomainForAccoutn: Call to DsGetDcNameWithAccountW failed with return vlalue 0 Unable to locate account FIMService My domain CORP has 2 WIndows Server 2008 R2 instances running and I am trying to set up an SPN for the FIMService on the non-DC instance. Please help Thanks 0 Question by:pdurbha Facebook Twitter LinkedIn Google LVL 17 Active today Best Solution bylruiz52 try setspn –S FIMService/servername.company.com domain\FIMService setspn –S FIMService/servername domain\FIMSservice Go to Solution 2 Comments LVL 17 Overall: Level 17 Windows Server 2008 6 Active Directory 5 Message Active today Accepted Solution by:lruiz522012-01-06 try setspn –S FIMService/servername.company.com domain\FIMService setspn –S FIMService/servername domain\FIMSservice 0 LVL 10 Overall: Level 10 MS Forefront-ISA 8 Windows Server 2008 5 Active Directory 2 Message Expert Comment by:simonlimon2012-01-09 http://technet.microsoft.com/en-us/library/ff512685(WS.10).aspx If
certificates to connect to the RMSwith a few agents reporting to the gateway in it's domain. I am http://www.networksteve.com/forum/topic.php/7016_-_The_Health_Service_cannot_verify_the_future_validity_of_t/?TopicId=44267&Posts=0 recieving this warning for all gateways and agents that are being monitored http://stackoverflow.com/questions/9666168/windows-2008-r1-suffers-recurring-error-81-when-running-diagnostics-unable-to (in the other domains). All our servers are either Win 2003 32bit or Win2003 64bit.The Health Service cannot verify the future validity of the RunAs account PRODUCTION\username for management group PRODMGMT due to an error retrieving information from Active Directory (for Domain Accounts) or the local ldap error security authority (for Local Accounts). The error is The network path was not found.(0x80070035).From the searching that I've done on the net, a couple of people have mentioned that if you set the password expiration flag on AD users and computers for the account the problem will go away.. This hasn't happened for me.I have checked the 0x51 server down logs on the gateway servers and they report the following messages:Event Type:ErrorEvent Source:HealthServiceEvent Category:Health Service Event ID:7016Date:15/03/2010Time:6:05:25 AMUser:N/AComputer:DEMOMMS003Description:The Health Service cannot verify the future validity of the RunAs account PRODUCTION\username for management group PRODMGMT due to an error retrieving information from Active Directory (for Domain Accounts) or the local security authority (for Local Accounts). The error is The network path was not found.(0x80070035). For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.Event Type:WarningEvent Source:HealthServiceEvent Category:Health Service Event ID:7020Date:15/03/2010Time:6:05:25 AMUser:N/AComputer:DEMOMMS003Description:The Health Service has validated all RunAs accounts for management group PRODMGMT, except those we could not monitor. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~However a few hours later I don't get any error messages and it seems to be working happily.Event Type:InformationEvent Source:HealthServiceEvent Category:Health Service Event ID:7026Date:15/03/2010Time:9:02:28 AMUser:N/AComputer:DEMOMMS003Description:The Health Service successfully logged on the RunAs account PRODUCTION\username for management group PRODMGMT For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.Event Type:InformationEvent Source:HealthServiceEvent Category:Health Service Event ID:7023Date:15/03/2010Time:9:02:28 AMUser:N/AComputer:DEMOMMS003Description:The Health Service has downloaded secure configuration for management group PRODMGM
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up WIndows 2008 R1 suffers recurring 'Error 81' when running diagnostics. Unable to connect to DC up vote 0 down vote favorite I've a recurring issue on a number of 2008 R1 servers. Replication stops completely, and any attempt to run any AD-related snap-ins or diagnostics fail. For example: C:\Windows\system32>dcdiag Directory Server Diagnosis Performing initial setup: Trying to find home server... Home Server = MYDC Ldap search capabality attribute search failed on server MYDC, return value = 81 Other tools also fail in the same manner: C:\Windows\system32>repadmin /showreps [d:\rtm\ds\ds\src\util\repadmin\repbind.c, 444] LDAP error 81 (Server Down) Win32 Err 58. LDP can't connect to the server either: ld = ldap_open("mydc", 389); Error <0x51>: Fail to connect to mydc. There are a couple of event log entries, but frankly I'm not sure if they are a cause or a symptom. Event 1311: The Knowledge Consistency Checker (KCC) has detected problems with the following directory partition. Directory partition: CN=Configuration,DC=ad,DC=mydomain,DC=co,DC=uk Event 1566: All directory servers in the following site that can replicate the directory partition over this transport are currently unavailable. Site: CN=MYSITE,CN=Sites,CN=Configuration,DC=ad,DC=mydomain,DC=co,DC=uk Directory partition: DC=ad,DC=mydomain,DC=co,DC=uk Transport: CN=IP,CN=Inter-Site Transports,CN=Sites,CN=Configuration,DC=ad,DC=mydomain,DC=co,DC=uk A reboot always clears this up, and always after a month or two the same problem will crop up again on a different server. I've seen it on 5 different servers in different domains so far. Reboots are fine, but it always feels like a bit of a blunt instrument. I was hoping someone might have come across this before and be able to offer a fix. thanks... windows-server-2008 share|improve this question asked Mar 12 '12 at 11:25 Smingos 12028 add a comment| 1 Answer 1 active oldest votes up vote 0 down vote Is this related to: "All th