Fsmocheck Error
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums Ask a question Quick access Forums home Browse forums users dcgetdcname(gc_server_required) call failed error 1355 FAQ Search related threads Remove From My Forums Answered by:
Dsgetdcname Call Failed Error 1355
Server Failed FSMO Test Windows Server > Directory Services Question 0 Sign in to fatal error:dsgetdcname call failed, error 1355 server 2012 vote Hello Thanks in advance for your help! So around early afternoon today, we lost the ability to login to the domain controller. dcdiag all gc are down error 1355 /test:fsmocheck gives me the following: Starting test: fsmo check 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 1355 A good time server could not be located. Warning:
Dcdiag Failed Test Locatorcheck
DCGetDCName (KDC_required) call failed, error 1355 A KDC could not be located - all the KDCs are down.
can appear: Starting test: Advertising The DC DC1 is advertising itself as a DC and having a DS. The DC DC1 is advertising as an LDAP server The DC DC1 is advertising as having a writeable directory The DC DC1 dcgetdcname(time_server) error 1355 is advertising as a Key Distribution Center Warning: DC1 is not advertising as a time the server holding the pdc role is down error 1355 server. The DS DC1 is advertising as a GC. ......................... DC1 failed test Advertisingche The exact command run to produce this test
Restart The Ntfrs Service
is: dcdiag /v /test:advertising FSMO Check Another error can appear within a different check in dcdiag: Starting test: FsmoCheck Warning: DcGetDcName(TIME_SERVER) call failed, error 1355 A Time Server could not be located. The server holding the https://social.technet.microsoft.com/Forums/windowsserver/en-US/744fb385-e8a8-402d-8053-9cf0496de13c/server-failed-fsmo-test?forum=winserverDS PDC role is down. Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error 1355 A Good Time Server could not be located. The exact command run to produce this test is: dcdiag /test:fsmocheck Cause The dcdiag tool detects that the time service is either not running or is running but not announcing itself as a reliable time server. Resolution Try each of these solutions one step at a time, re-testing after completing each step until the problem is http://ben.goodacre.name/tech/Domain_Controller_is_not_advertising_as_a_time_server_Error_in_dcdiag_(Windows) resolved. Ensure the Windows Time service is running. On a DC it is part of the core AD functonality and should be runing even if synchronised time is not essential.net start w32time Restart the Windows time servicenet stop w32time && net start w32time Check that Network problems are not stopping NTP form functioning. Note that Windows clients do not synchronise with the DCs via NTP, this only tests the ability for DC themselves to check an external time source:w32tm /stripchart /computer:time.windows.com /samples:2 /dataonlyError 0x800705B4 is a network timeout on the port - 123. Time.winfows.com should be replaced with the external time server you are using for a more complete test. Try: netdiag /fix Netdiag is part of Windows Server 2003 Service Pack 1 Support Tools. This can also be used on Server 2008. If you received the error message: The service name is invalid earlier the Windows Time service is not even registered. Re-registering the W32time service can also fix some issues so perform these steps anyway: Re-registering the Windows Time Service Try:w32tm /resync /redisscover Check that the DC has the PDC role: netdom query fsmoIf it is run the following command:w32tm /config /manualpeerlist:time.windows.com /syncfromflags:manual /reliable:yes /update Microsoft's own free NTP server can be used as shown here, but I would recommend using one in your country if
single Active Directory domain with a single forest. This domain has a central site and approximately15 remote branch sites in a hub http://clintboessen.blogspot.com/2013/11/the-server-holding-pdc-role-is-down.html 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 A Time Server could not be located. The server holding the PDC role error 1355 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 not configured to sync to an external time source (common configuration requirement in all AD domains). What was most concerning call failed error 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 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