Error 1355 Time Server
Contents |
failed, error 1355 A Good Time Server could not be located. ----- Quick resolution worked for me changing time server: The procedure for doing this on a PDC Emulator running Windows Server 2003 in the forest error 1355 a time server could not be located root domain is as follows. Open Registry Editor (regedit.exe) and configure the following registry
Error 1355 Server 2012
entries: HKLM\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\Type This registry entry determines which peers W32Time will accept synchronization from. Change this REG_SZ value from NT5DS to NTP
Error 1355 The Locator Could Not Find The Server
so the PDC Emulator synchronizes from the list of reliable time servers specified in the NtpServer registry entry described below. HKLM\SYSTEM\CurrentControlSet\Services\W32Time\Config\AnnounceFlags This registry entry controls whether the local computer is marked as a reliable time
Supersocket Info (spnregister) Error 1355
server (which is only possible if the previous registry entry is set to NTP as described above). Change this REG_DWORD value from 10 to 5 here. HKLM\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\NtpServer This registry entry specifies a space-delimited list of stratum 1 time servers from which the local computer can obtain reliable time stamps. The list may consist of one or more DNS names or IP addresses (if DNS names are used then you error 1355 domain join must append ,0x1 to the end of each DNS name). For example, to synchronize the PDC Emulator in your forest root domain with tock.usno.navy.mil, an open-access SNTP time server run by the United States Naval Observatory, change the value of the NtpServer registry entry from time.windows.com,0x1 to tock.usno.navy.mil,0x1 here. Alternatively, you can specify the IP address of this time server, which is 192.5.41.209 instead. Now stop and restart the Windows Time service using the following commands: net stop w32time net start w32time Tagged with: Categorised as: Microsoft, Networking, Windows Upgrade Leave a Reply Cancel replyYou must be logged in to post a comment. Search for: September 2009 M T W T F S S « Aug Oct » 123456 78910111213 14151617181920 21222324252627 282930 Categories App V blogmail Cisco Exchange Hardware/Software Juniper Linux/OSX LYNC Microsoft Networking OS X Outlook Password Recovery Server OS Virtual Infrastructure VMWare/ESX Windows Upgrade Blogroll En Route Blog En Route Main Site Login Michal Shuans blog Support Forum CloudAppleTV enable USB storage AppleTV | AppleTV Firmware Download Locations Hacking Apple TV Take 2 Tutorial Archives Archives Select Month August 2016 July 2016 May 2016 April 2016 March 2016 November 2015 August 2015 July 2015 May 2015 April 2015 March 2015 February 20
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 error 1355 the specified domain directory The DC DC1 is advertising as a Key Distribution Center Warning: DC1 is error 1355 pdc role is down not advertising as a time server. The DS DC1 is advertising as a GC. ......................... DC1 failed test Advertisingche The exact error 1355 dcdiag 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 http://blog.shiraj.com/2009/09/dcgetdcnametime_server-call-failed-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 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 /manualpeerlist:time.windows.com /syncf
single Active Directory domain with a single forest. This domain has a central site and approximately15 remote branch sites http://clintboessen.blogspot.com/2013/11/the-server-holding-pdc-role-is-down.html in a hub and spoke type deployment. When running a FSMO https://www.experts-exchange.com/questions/25094646/Warning-DcGetDcName-TIME-SERVER-call-failed-error-1355.html 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 error 1355 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 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 error 1355 the configuration requirement in all AD domains). What was most concerning 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
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 Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Warning: DcGetDcName(TIME_SERVER) call failed, error 1355 Want to Advertise Here? Solved Warning: DcGetDcName(TIME_SERVER) call failed, error 1355 Posted on 2010-01-28 MS Legacy OS Active Directory Windows Server 2003 2 Verified Solutions 8 Comments 3,952 Views Last Modified: 2012-11-06 Running dcdiag on a windows 2003 native AD domain.. Simple, one domain, one forest, three domain controllers all of them GCs. Every AD server returns this error: DC1 is not advertising as a time server. And this: 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 1355 A Good Time Server could not be located. I have done all of this: http://ben.goodacre.name/tech/Domain_Controller_is_not_advertising_as_a_time_server_Error_in_dcdiag_(Windows) Netdom query pdc runs fine on all of the servers, returns the correct pdc emulator. Everything seems to be fine except that error in dcdiag and Event ID: 14 is in one AD server's log multiple times: The time provider NtpClient was unable to find a domain controller to use as a time source. NtpClient will try again in 240 minutes. This server is on a different subnet than the other two. I just ran w32tm on the other AD server (non pdc emulator) and it returned 'the computer did not resync because no time data was available' and logged an event id: 14 in the system log. This one has me stumped.. any ideas how to fix this? I want to upgrade the domain to AD 2008, but am afraid to with this happening. 0 Question by:H2Omike Facebook Twitter LinkedIn Google LVL 24 Best Solution byAwinish The error related due to time sync issue. Please check port 123 tcp as well as UDP has been opened on DC for inbound & outbound conne