A Good Time Server Could Not Be Located Error 1355
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: A time server could not be located error message... Windows Server > dcgetdcname(pdc_required) call failed error 1355 Directory Services Question 0 Sign in to vote Hi all; I have a dcgetdcname time_server call failed error 1355 parent-child domain design with Windows Server 2003 R2 SP2 in place. Some days ago, when I executed the dcdiag on my
Dcdiag Error 1355
child domain controller, the following error message appeared in the result: tarting test: FsmoCheck Warning: DcGetDcName(TIME_SERVER) call failed, error 1355 A Time Server could not be
The Server Holding The Pdc Role Is Down
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. Why would my "only" DC not be advertising as a time server? When I see the status of the Windows Time service in Services.msc it is started. Any idea? Thanks Changed the computer did not resync because no time data was available type R.Alikhani Friday, May 28, 2010 8:37 AM Monday, May 24, 2010 8:08 PM Reply | Quote Answers 0 Sign in to vote There are several steps required, take a look at Matt's entry (with links to the official time blogs entry also) http://tigermatt.wordpress.com/2009/08/01/windows-time-for-active-directory/ One thing I would suggest is if your time is right now within five minutes the bigger priority would be to get a second DC up in that child domain. Your single DC goes down hard and crashes and you have bigger issues and outage time. That second DC is a nice insurance policy. Thanks Mikehttp://adisfun.blogspot.com; Proposed as answer by Meinolf WeberMVP Sunday, May 30, 2010 11:29 AM Marked as answer by R.Alikhani Monday, May 31, 2010 6:51 AM Friday, May 28, 2010 6:46 PM Reply | Quote 0 Sign in to vote Sorry for the long delay; Yes, this DC is the PDC Emulator role holder. There are only one DC in the child domain. Now, how can i configure Windows time hierarchy on my forest? Thanks Hello imprise, In addition to Mike's suggestions, please read my blog on the time service, and how to configure it. It also explains how child domains work in the time s
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 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,904 Views Last https://social.technet.microsoft.com/Forums/windowsserver/en-US/e78cc839-8c12-4886-8ff7-ed537f75ae69/a-time-server-could-not-be-located-error-message?forum=winserverDS 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 - I https://www.experts-exchange.com/questions/27322087/DCDiag-reports-'a-good-time-server-could-not-be-located'-and-'the-PDC-role-is-down'.html 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: Advertising
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 is advertising as a http://ben.goodacre.name/tech/Domain_Controller_is_not_advertising_as_a_time_server_Error_in_dcdiag_(Windows) 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 not be located. The server holding the PDC role is down. Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error error 1355 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 resolved. Ensure the Windows Time service is running. On a DC it call failed error 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 not in thr US. For the UK I can recommend ntp2d.mcc.ac.uk but there are many others. Ensure that the DC is announcing itself correctly thro