Dcdiag Time Server 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 > Directory Services Question dcdiag error 1355 all gc are down 0 Sign in to vote Hi all; I have a parent-child domain design
Dcdiag Fsmocheck Failed Error 1355
with Windows Server 2003 R2 SP2 in place. Some days ago, when I executed the dcdiag on my child domain controller, the
Dcgetdcname(pdc_required) Call Failed, Error 1355
following error message appeared in the result: tarting test: FsmoCheck Warning: DcGetDcName(TIME_SERVER) call failed, error 1355 A Time Server could not be located.
Dcdiag Failed Test Locatorcheck
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 type R.Alikhani Friday, May 28, 2010 8:37 AM the server holding the pdc role is down 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 service hierarchy. I hope you find it helpful. Configuring the Windows Time Service for Windows Server http://msmvps.com/blogs/acefek
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 dcdiag error 1355 The DC DC1 is advertising as a Key Distribution Center Warning: DC1 is warning dcgetdcname(time_server) call failed error 1355 not advertising as a time server. The DS DC1 is advertising as a GC. ......................... DC1 failed test Advertisingche The exact dcdiag /test:advertising 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 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 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 at http://ben.goodacre.name/tech/Domain_Controller_is_not_advertising_as_a_time_server_Error_in_dcdiag_(Windows) 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 /syncfromflags:manual
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 Close Search Login Join Today Products BackProducts https://www.experts-exchange.com/questions/28188698/Error-with-PDC-and-Time-server-win2008-r2.html Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Error with PDC and Time server win2008 r2 Want to Advertise Here? Solved Error with PDC and Time server win2008 r2 Posted on 2013-07-18 MS Legacy OS MS Server OS Windows Server 2008 1 Verified Solution 8 Comments 1,878 Views Last Modified: 2013-07-18 I have been having issues with my Windows 2008 R2 AD DS after having a 2003 AD fail and had to be removed error 1355 using dcpromo /forceremoval. The server gives the following information when using the commands listed. The name of the Domain controller was changed and the domain was changed as seen. I have tried doing several things with the DNS by manually removing the references to the old Controller. I have also restarted the time service with net stop w32time and net start w32time which did not fix any problems. I need to get this fixed prior to adding a second windows 2008 R2 dcdiag error 1355 DC. Please help as I have been working on this for several days. C:\>dcdiag /q Warning: