Dcgetdcname Call Failed Error
Contents |
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: FSMO Roles Windows Server > Directory Services Question 0 Sign in to vote Hi I got thid issue when
Dcdiag Failed Test Locatorcheck
runing DCDIAG, any helps please Starting test: FsmoCheck Warning: DcGetDcName(PDC_REQUIRED) call failed, all gc are down error 1355 error 1355 A Primary Domain Controller could not be located. The server holding the PDC role is down. error 1355 server 2012 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 135 5 A Good Time
The Server Holding The Pdc Role Is Down Error 1355
Server could not be located. Thursday, October 04, 2012 5:06 PM Reply | Quote Answers 0 Sign in to vote Hi, "The server holding the PDC role is down" On the server holding the PDC emulator role, check whether the Windows Time service is started. Also check on the server on which the dcdiag was run..(if it is not the PDC emulator) To find PDC emulator, at the command line
Dsgetdcname Call Failed Error 1355
on a DC run the following Netdom query fsmo To check the status of the Windows Time service Go to Administrative Tools -> Services Ensure that the Windows Time service is set to automatic start up and that it is started. Reboot the server then run the dcdiag test again.SelloD Proposed as answer by Cicely FengModerator Friday, October 05, 2012 2:45 AM Marked as answer by Cicely FengModerator Monday, October 15, 2012 7:27 AM Thursday, October 04, 2012 8:04 PM Reply | Quote 0 Sign in to vote Hi, It seems the "Authorative Time server" is not configured or down. Please run "netdom query dc" command and verify the PDC emulator role owner DC name and ensure that it is online and Windows Time service is in started state. AlsoPDC role owner in forest root domain should be configured as an authorative time server other DCs should sync with PDC and domain members should sync with DCs. Run following commands: On PDC emulator: w32tm /config /manualpeerlist:time.windows.com,0×1 /syncfromflags:manual /reliable:yes /update net stop w32time & net start w32time & w32tm /resync /rediscover On Non -PDC DC and Domain Clients: w32tm /config /syncfromflags:domhier /update net stop w32time & net start w32time & w32tm /resync /rediscover Once done with abov
360 games PC games dcgetdcname(time_server) call failed error 1355 Windows games Windows phone games Entertainment All Entertainment
Fatal Error:dsgetdcname Call Failed, Error 1355 Server 2012
Movies & TV Music Business & Education Business Students & educators dcdiag error 1355 Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet https://social.technet.microsoft.com/Forums/en-US/b4febe07-bff1-4e8d-a9c7-9a1fb1cc262e/fsmo-roles?forum=winserverDS Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Lumia All https://support.microsoft.com/en-us/kb/958804 Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
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 http://blog.shiraj.com/2009/09/dcgetdcnametime_server-call-failed-error-1355/ 2003 in the forest root domain is as follows. Open Registry Editor (regedit.exe) http://clintboessen.blogspot.com/2013/11/the-server-holding-pdc-role-is-down.html and configure the following registry 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 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 error 1355 the local computer is marked as a reliable time 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 call failed error more DNS names or IP addresses (if DNS names are used then you 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
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 running a FSMO 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 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 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