Domain Controller Error 1355
Contents |
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs Ask a question Quick access Forums home Browse forums users FAQ dcgetdcname(gc_server_required) call failed error 1355 Search related threads Remove From My Forums Answered all gc are down error 1355 by: DCDIAG showing multiple errors for enterprise tests - error 1355 Windows warning dcgetdcname(time_server) call failed error 1355 Server > Directory Services Question 0 Sign in to vote Hello there, Am hoping someone can help... On 1 of my the server holding the pdc role is down error 1355 2008 R2 DCs (AV2) I'm seeing multiple errors for enterprise tests from DCDIAG (please see output below). The errors are mainly 1355 and they sound quite serious ("A Primary Domain Controller could not be located", "The server holding the PDC role is
Dcdiag Failed Test Locatorcheck
down."). In Event Viewer on my AV2 server I'm also seeing errors 1202 (Active Directory Web Services) and 8016 (related to my Sophos anti-virus management console). These issues seemed to have cropped up after installing a bunch of Microsoft updates. Thanks in advance for any feedback. C:\Users\admin1.mydomain>netdom query fsmo Schema master FS1.mydomain.com Domain naming master FS1.mydomain.com PDC FS1.mydomain.com RID pool manager FS1.mydomain.com Infrastructure master FS1.mydomain.com The command completed successfully. C:\Users\admin1.mydomain> C:\Users\admin1.mydomain> C:\Users\admin1.mydomain>dcdiag Directory Server Diagnosis Performing initial setup: Trying to find home server... Home Server = AV2 * Identified AD Forest. Done gathering initial info. Doing initial required tests Testing server: Default-First-Site-Name\AV2 Starting test: Connectivity ......................... AV2 passed test Connectivity Doing primary tests Testing server:
Start 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
Fatal Error:dsgetdcname
about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered error 1355 server 2012 Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign a primary domain controller could not be located. the server holding the pdc role is down up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Domain Controller DCdiag error - A Global Catalog Server could not be located up https://social.technet.microsoft.com/Forums/en-US/54400c1c-d543-481d-8527-278587040a7e/dcdiag-showing-multiple-errors-for-enterprise-tests-error-1355?forum=winserverDS vote 3 down vote favorite 1 I've set up a replica DC in a remote location. It's connected to the main site through a VPN connection. DCdiag passes on the primary DC, but I get the following error on the replica DC: Running enterprise tests on : mydomain.co.uk Starting test: LocatorCheck Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355 A Global Catalog Server could not be located - All GC's are down. Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355 A Primary http://serverfault.com/questions/370314/domain-controller-dcdiag-error-a-global-catalog-server-could-not-be-located Domain Controller could not be located. The server holding the PDC role is down. ......................... mydomain.co.uk failed test LocatorCheck Is it giving this error just because it is not the global catalogue server, or is there some connectivity issue where it does not think there is one at all, as the error seems to imply? If so, it seems odd, as all other tests were passed. What do I do about this? windows-server-2008-r2 domain-controller active-directory share|improve this question asked Mar 16 '12 at 2:35 paradroid 62931022 How's DNS set up on the replica? –Shane Madden♦ Mar 16 '12 at 2:58 @ShaneMadden: It was set up through netdom join. I assumed that was all that was needed. The DNS entries appear to have been replicated, apart from the DCs themselves (the original DC appears on both DNS databases, but the replica only appears through dig on the original, but with two entries, one being an out-of-date address). –paradroid Mar 16 '12 at 3:24 1 Are you in some kind of recovery scenario? The server is doing SRV record lookups to try and find the server holding the PDC Emulator FSMO role as well as looking for a Global Catalog server. I believe Shane was referring to the DNS client settings on the NIC of the remote server. –SpacemanSpiff Mar 16 '12 at 3:42 @SpacemanSpiff: I
single Active Directory domain with a single forest. This domain has a central site and http://clintboessen.blogspot.com/2013/11/the-server-holding-pdc-role-is-down.html approximately15 remote branch sites in a hub and spoke type deployment. When running a FSMO role check using DCDiag on any domain controller in the domain, all domain controllers complained the PDC role is down. This error experienced below was experienced on all domain controllers throughout the domain. dcdiag /test:FSMOcheck Warning: DsGetDcName(TIME_SERVER) call failed, error 1355 error 1355 A Time Server could not be located. The server holding the PDC role is down. Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error 1355. A Good Time Server could not be located. The time errors just mean the domain time hierarchy is not configured correctly, most likely cause is the PDC emulator in the forest root call failed error domain is not configured to sync to an external time source (common configuration requirement in all AD domains). What was most concerning however is the error "The server holding the PDC role is down". Testing the PDC emulator, I could connect to it using MMC snap-ins such as Active Directory Users and Computers and verified the PDC Emulator domain controller was processing authentication requests. Why is this error saying it is down? Next I performed a test to verify if the PDC emulator is working correctly. The PDC Emulator has many roles including being the source of authority for domain group policy changes, the source of authority for time synchronisation and being a reliable source for all password synchronization. For example, all password changes performed by other DCs in the domain are immediately replicated to the PDC emulator role. If a logon authentication fails at a given DC in a domain due to a bad password, the DC will forward the authentication reques