Dcdiag Error 1355 Pdc_required
Contents |
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: FSMO Roles Windows Server > Directory Services Question 0 Sign in to vote Hi I got thid
Dcdiag Error 1355 All Gc Are Down
issue when runing DCDIAG, any helps please Starting test: FsmoCheck Warning: DcGetDcName(PDC_REQUIRED) call dcdiag fsmocheck failed error 1355 failed, error 1355 A Primary Domain Controller could not be located. The server holding the PDC role is dcdiag failed test locatorcheck down. Warning: DcGetDcName(TIME_SERVER) call failed, 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 135 5
All Gc Are Down Error 1355
A Good Time Server could not be located. Thursday, October 04, 2012 5:06 PM Reply | Quote Answers 0 Sign in to vote Hi, "The server holding the PDC role is down" On the server holding the PDC emulator role, check whether the Windows Time service is started. Also check on the server on which the dcdiag was run..(if it is not the PDC emulator) To find PDC emulator,
The Server Holding The Pdc Role Is Down Error 1355
at the command line on a DC run the following Netdom query fsmo To check the status of the Windows Time service Go to Administrative Tools -> Services Ensure that the Windows Time service is set to automatic start up and that it is started. Reboot the server then run the dcdiag test again.SelloD Proposed as answer by Cicely FengModerator Friday, October 05, 2012 2:45 AM Marked as answer by Cicely FengModerator Monday, October 15, 2012 7:27 AM Thursday, October 04, 2012 8:04 PM Reply | Quote 0 Sign in to vote Hi, It seems the "Authorative Time server" is not configured or down. Please run "netdom query dc" command and verify the PDC emulator role owner DC name and ensure that it is online and Windows Time service is in started state. AlsoPDC role owner in forest root domain should be configured as an authorative time server other DCs should sync with PDC and domain members should sync with DCs. Run following commands: On PDC emulator: w32tm /config /manualpeerlist:time.windows.com,0×1 /syncfromflags:manual /reliable:yes /update net stop w32time & net start w32time & w32tm /resync /rediscover On Non -PDC DC and Domain Clients: w32tm /config /syncfromflags:domhier /update net stop w32time & net start w32tim
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 error 1355 server 2012 Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags
Dcgetdcname(time_server) Call Failed Error 1355
Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only a primary domain controller could not be located 1355 takes a minute: Sign 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 https://social.technet.microsoft.com/Forums/en-US/b4febe07-bff1-4e8d-a9c7-9a1fb1cc262e/fsmo-roles?forum=winserverDS could not be located up 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: http://serverfault.com/questions/370314/domain-controller-dcdiag-error-a-global-catalog-server-could-not-be-located DcGetDcName(PDC_REQUIRED) call failed, error 1355 A Primary 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
single Active Directory domain with a single forest. This domain has a central site and approximately15 remote branch sites in a hub and spoke type deployment. When running a FSMO role check using DCDiag on any domain http://clintboessen.blogspot.com/2013/11/the-server-holding-pdc-role-is-down.html controller in the domain, all domain controllers complained the PDC role is down. This error http://www.vistax64.com/sbs-server/254125-cannot-locate-global-catalog-server-error-1355-dcdiag.html experienced below was experienced on all domain controllers throughout the domain. dcdiag /test:FSMOcheck Warning: DsGetDcName(TIME_SERVER) call failed, 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 error 1355 likely cause is the PDC emulator in the forest root 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 dcdiag error 1355 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 request to the PDC emulator to validate the request against the most current password. Using this understanding around how the PDC emulator works, I performed a password change on a remote domain controller in another Active Directory site which has a replication interval of 3 hours. I then attempted to login using the user account changed password in a different AD site using a domain controller which does not have the updated password. I verified the request went to the PDC emulator to validate the users password has changed - hence the PDC emulator is in working order. Also querying the PDC emulator with netdom returned it successfully. Why are all domain controllers complaining the PDC role is down when doing a DCDiag? The Resolution I first went to tackle the time issue. After
locate Global Catalog server error 1355 from dcdiag Cannot locate Global Catalog server error 1355 from dcdiag New 15 Sep 2009 #1 George Guest Cannot locate Global Catalog server error 1355 from dcdiag Hello, I'm running Windows SBS 2003 SP2. This is the only server up and running in my domain. This morning users reported slow login times. The application log shows two errors every 5 minutes: event ID 1006 Windows cannot bind to mydomain domain. (Local Error). Group Policy processing aborted. and event ID 1030 Windows cannot query for the list of Group Policy objects. Check the event log for possible messages previously logged by the policy engine that describes the reason for this. I also have this error once in the system log: event ID 16645 The maximum account identifier allocated to this domain controller has been assigned. The domain controller has failed to obtain a new identifier pool. A possible reason for this is that the domain controller has been unable to contact the master domain controller. Account creation on this controller will fail until a new pool has been allocated. There may be network or connectivity problems in the domain, or the master domain controller may be offline or missing from the domain. Verify that the master domain controller is running and connected to the domain. At 4:30am my time I had the 16645, the other two started appearing two minutes later and are still appearing every 5 minutes. I ran dcdiag and saw this in the output: Starting test: FsmoCheck 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 Domain Controller could not be located. The server holding the PDC role is down. Warning: DcGetDcName(TIME_SERVER) call failed, error 1355 A Time Server could not be located. The server holding the PDC role is down. Warning: DcGetDcName(KDC_REQUIRED) call failed, error 1355 A KDC could not be located - All the KDCs are down. ......................... mydomain failed test FsmoCheck I am now wondering what course of action I should take. I have backups of the system state but I'm wondering if there's something else I could to to fix this. I don't even know how it might have happened as I've made no changes on the server. I've tried restarting the DNS server service and the netlogon service, no good. I can also access \\myserver\netlogon and \\myserver\sy