Dcdiag Dcgetdcnametime_server Call Failed Error 1355
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums Ask a question Quick access Forums home Browse forums users FAQ Search warning dcgetdcname(pdc_required) call failed error 1355 related threads Remove From My Forums Answered by: Server Failed warning dcgetdcname(gc_server_required) call failed error 1355 FSMO Test Windows Server > Directory Services Question 0 Sign in to vote Hello Thanks
Dcgetdcname(pdc_required) Call Failed Error 1355
in advance for your help! So around early afternoon today, we lost the ability to login to the domain controller. dcdiag /test:fsmocheck gives me
Failed Test Locatorcheck
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: DCGetDCName (KDC_required) call failed, error dcdiag error 1355 1355 A KDC could not be located - all the KDCs are down.
‘A Good Time server could not be located' Home » Microsoft » Windows - Error ‘A Good Time server could not be located' KB ID 0000705
The Server Holding The Pdc Role Is Down
Dtd 06/11/12 Problem Seen when running dcdiag, Error(s): Starting test: Advertising Warning: dcdiag test Server-Name is not advertising as a time server. ......................... Server-Name failed test Advertising Running enterprise tests on : the computer did not resync because no time data was available PeteNetLive.com Starting test: Intersite ......................... PeteNetLive.com passed test Intersite Starting test: FsmoCheck Warning: DcGetDcName(TIME_SERVER) call failed, error 1355 A Time Server could not be located. The server holding the PDC https://social.technet.microsoft.com/Forums/windowsserver/en-US/744fb385-e8a8-402d-8053-9cf0496de13c/server-failed-fsmo-test?forum=winserverDS role is down. Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error 1355 A Good Time Server could not be located. ......................... PeteNetLive.com failed test FsmoCheck Solution Note: Any one of the things below can cause this problem, I suggest you retry running dcdiag after each step until it runs without error. 1. In a windows domain, clients normally get their time from the domain http://www.petenetlive.com/KB/Article/0000705 controller that holds the PDC Emulator role. Locate that server and log on. Locate your FSMO Role Servers 2. Now configure your PDC emulator to get its time from a reliable external source. Windows - Setting Domain Time 3. If you have got this far, then should already have the windows time service running, check! 4. From command line, remove and reinstall the Windows time service with the following two commands. w32tm /unregister
w32tm /register Note: It's not unusual to see the following error after you issue a 'w32tm /unregister' command, Error The following error occurred: Access is denied (0x80070005) If this happens don't panic, open the services console (Press F5) and the Windows Time Service may have disappeared (if so re-register it). If not manually stop the Windows Time service and try to unregister again, then re-register. WARNING: After doing this, you will need to set the time service to get reliable time from an NTP External Server again. 5. Press Windows Key+R > regedit {enter} > Navigate to the following registry key; HKLM > System > Curren
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 http://ben.goodacre.name/tech/Domain_Controller_is_not_advertising_as_a_time_server_Error_in_dcdiag_(Windows) directory The DC DC1 is advertising as a Key Distribution Center Warning: DC1 is not advertising as a time server. The DS DC1 is advertising as a GC. ......................... DC1 failed test Advertisingche The exact command run to produce this test 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 error 1355 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 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 call failed error at a time, re-testing after completing each step until the problem is 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 /syncfromflag