Dcdiag Error 1355 Pdc
Contents |
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: DCDIAG showing multiple errors for enterprise tests -
Dcdiag Error 1355 All Gc Are Down
error 1355 Windows Server > Directory Services Question 0 Sign in dcdiag fsmocheck failed error 1355 to vote Hello there, Am hoping someone can help... On 1 of my 2008 R2 DCs (AV2) I'm error 1355 pdc role is down 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
Dcgetdcname(gc_server_required) Call Failed Error 1355
located", "The server holding the PDC role is 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
Dcdiag Failed Test Locatorcheck
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: Default-First-Site-Name\AV2 Starting test: Advertising Warning: AV2 is not advertising as a time server. ......................... AV2 failed test Advertising Starting test: FrsEvent ......................... AV2 passed test FrsEvent Starting test: DFSREvent ......................... AV2 passed test DFSREvent Starting test: SysVolCheck ......................... AV2 passed test SysVolCheck Starting test: KccEvent ......................... AV2 passed test KccEvent Starting test: KnowsOfRoleHolders ......................... AV2 passed test KnowsOfRoleHolders Starting test: MachineAccount ......................... AV2 passed test MachineAccount Starting test: NCSecDesc Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have Replicating Directory Changes In Filtered Set access
single Active Directory domain with a single forest. This domain has a central site and the server holding the pdc role is down error 1355 approximately15 remote branch sites in a hub and spoke type deployment.
All Gc Are Down Error 1355
When running a FSMO role check using DCDiag on any domain controller in the domain, all domain a primary domain controller could not be located 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 https://social.technet.microsoft.com/Forums/en-US/54400c1c-d543-481d-8527-278587040a7e/dcdiag-showing-multiple-errors-for-enterprise-tests-error-1355?forum=winserverDS 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 domain is http://clintboessen.blogspot.com/2013/11/the-server-holding-pdc-role-is-down.html 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 request to the PDC
Off on What to do when the Domain Controller Can't find its domain! PROBLEM: Users unable to login to the domain - DCs not replicating RESOLUTION: => Set the RPC Locator service to Automatic and started on http://www.shofkom.com/2009/03/10/what-to-do-when-the-domain-controller-cant-find-its-domain/ the PDC. => Still DCdiag gave errors of 1355. => Ran dcdiag on both PDC and BDC - both showed problems with sysvol and netlogon shares => Checked and found that both servers did not have sysvol and netlogon shared => Found that the SYSVOL was shared as SYSVOLa - unshared it as it looked like manually shared. => Checked the PDC server and found that the Policies and Scripts were under the NTFRS-PRE-Existing error 1355 folder => Stopped FRS Service on the BDC and PDC servers => Backed the policies and scripts from ntfrs-pre-existing folders to a folder on the desktop on PDC => Copied it on to the SYSVOL\sysvol folder => Started the FRS Service only on PDC => The sysvol and netlogon shares did not get created. => Stopped FRS Service again on PDC => On registry modified the following : HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup Burflags value to d4 dcdiag error 1355 => Started the FRS service on PDC => Got Event id : 13516 NTFRS on the PDC File replication service event log => On the BDC modified the registry : HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup Burflags value to d2 => Started FRS Service on BDC => Got Event id : 13516 NTFRS on the BDC File Replication service event log => Checked replication using repadmin /syncall - looks fine on both servers => Ran dcdiag /q on BDC and got no errors => Ran dcdiag /q on PDC and got one warning of 13508 and 13509 being reported on the eventlogs => Restarted FRS service on the PDC and reran dcdiag /q - got no errors now => All looks fine I researched the Event ID received from the following portion of a dcdiag on PDC: 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(TIME_SERVER) call failed, error 1355 A Time Server could not be located. The server holding the PDC role is down. http://technet2.microsoft.com/windowsserver/en/library/ce8890cf-ef46-4931-8e4a-2fc5b4ddb0471033.mspx?mfr=true http://technet2.microsoft.com/windowsserver/en/library/b43a025f-cce2-4c82-b3ea-3b95d482db3a1033.mspx?mfr=true At first I believed the problem to be related to users being unable to access the PDC's time server service. It appears that all systems were referring to the BDC for time server requests in the domain. RJ initiated a call to Microsoft (case#SRX08062460