Error 1355 A Time Server Could Not Be Located
Contents |
‘A Good Time server could not be located' Home » Microsoft » Windows - Error ‘A Good Time dcgetdcname(gc_server_required) call failed error 1355 server could not be located' KB ID 0000705 Dtd 06/11/12
Dcgetdcname Time_server Call Failed Error 1355
Problem Seen when running dcdiag, Error(s): Starting test: Advertising Warning: Server-Name is not advertising as a failed test locatorcheck time server. ......................... Server-Name failed test Advertising Running enterprise tests on : PeteNetLive.com Starting test: Intersite ......................... PeteNetLive.com passed test Intersite Starting test: FsmoCheck Warning: DcGetDcName(TIME_SERVER) dcdiag error 1355 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. ......................... PeteNetLive.com failed test FsmoCheck Solution Note: Any one of the things below can cause this problem, I suggest
The Server Holding The Pdc Role Is Down
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 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
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 the computer did not resync because no time data was available 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 http://www.petenetlive.com/KB/Article/0000705 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 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 http://ben.goodacre.name/tech/Domain_Controller_is_not_advertising_as_a_time_server_Error_in_dcdiag_(Windows) 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 /
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit https://www.experts-exchange.com/questions/27322087/DCDiag-reports-'a-good-time-server-could-not-be-located'-and-'the-PDC-role-is-down'.html Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > DCDiag reports 'a good time server could not be located' and 'the PDC role is down' Want to Advertise Here? Solved DCDiag reports 'a good time server could not be located' and 'the PDC role is down' Posted on 2011-09-22 Windows Server 2008 Active Directory 2 Verified Solutions 37 Comments 2,918 Views error 1355 Last Modified: 2012-11-06 I had a backup domain controller have issues which caused me to demote it, unjoin it from the domain, and then join again as a member server. Since then it seems, the timer server service has not worked. Last night I promoted the backup to domain controller again (I only have 2 servers so needed to be done) but the problem persists. I have tried everything I can find to try - call failed error I have checked and double-checked all the registry entries defined by Microsoft to set up for a time server and I have stopped, config'd, restarted the time service at command prompt every which way I can find to do so - i.e. http://ben.goodacre.name/tech/Domain_Controller_is_not_advertising_as_a_time_server_Error_in_dcdiag_(Windows) . Also DCDiag reports at the beginning that it is not advertising as a time server. All the FSMO roles are correct and there are no other DCDiag issues. What else can I do?! 0 Question by:DSpiegl Facebook Twitter LinkedIn Google Best Solution byDSpiegl Odd? I kept doing dcdiag's and it would report all the dc errors as before and then it would go back to looking clean. Never did so many dcdiags so don't know how unusual that is. Anyway,found Go to Solution 37 Comments LVL 59 Overall: Level 59 Windows Server 2008 47 Active Directory 28 Message Expert Comment by:Darius Ghassem2011-09-22 Run netdom query fsmo Post dcdiag 0 Message Author Comment by:DSpiegl2011-09-22 Directory Server Diagnosis Performing initial setup: Trying to find home server... Home Server = SMCSERVER * Identified AD Forest. Done gathering initial info. Doing initial required tests Testing server: Default-First-Site\SMCSERVER Starting test: Connectivity ......................... SMCSERVER passed test Connectivity Doing primary tests Testing server: Default-First-Site\SMCSERVER Starting test: Advertisin