Dcgetdcname Time_server Call Failed Error 1355
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 root domain error 1355 pdc role is down is as follows. Open Registry Editor (regedit.exe) and configure the following registry entries: HKLM\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\Type
Dcgetdcname Time Server Call Failed
This registry entry determines which peers W32Time will accept synchronization from. Change this REG_SZ value from NT5DS to NTP so the dcgetdcname(pdc_required) call failed error 1355 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 server (which is failed test locatorcheck 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 must append ,0x1 to the
Dcdiag Error 1355
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 2015 January 2015 November 2014 October 2014 September 2014 Jul
‘A Good Time server could not be located' Home » Microsoft » Windows - Error ‘A Good Time the server holding the pdc role is down server could not be located' KB ID 0000705 Dtd 06/11/12 dcdiag test Problem Seen when running dcdiag, Error(s): Starting test: Advertising Warning: Server-Name is not advertising as a
The Computer Did Not Resync Because No Time Data Was Available
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) http://blog.shiraj.com/2009/09/dcgetdcnametime_server-call-failed-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 http://www.petenetlive.com/KB/Article/0000705 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 W
single Active Directory domain with a single forest. This domain has a central site and approximately15 remote branch sites in a hub and spoke type deployment. When http://clintboessen.blogspot.com/2013/11/the-server-holding-pdc-role-is-down.html running a FSMO role check using DCDiag on any domain controller in the domain, https://www.petri.com/forums/forum/server-operating-systems/windows-server-2000-2003-2003-r2/58434-warning-dcgetdcname-good_time_server_preferred-call-failed-error-1355 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 located. The server holding the PDC role is down. Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error 1355. A Good Time error 1355 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 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, call failed error 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 performed a password change on a remote domain controller in another Active Directory site which has a replication interval of 3 hours. I then attempted to login using the user account changed password in a different AD site using a domain controller which does not have the updated password. I verified the req