Dcgetdcname Pdc_required Call Failed Error 1355
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 netdom query pdc fails thid issue when runing DCDIAG, any helps please Starting test: FsmoCheck Warning:
Dcgetdcname Pdc Required Call Failed Error 1355 2003
DcGetDcName(PDC_REQUIRED) call failed, error 1355 A Primary Domain Controller could not be located. The server holding the PDC dcdiag failed test locatorcheck role is down. 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
All Gc Are Down Error 1355
5 A Good Time 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) the server holding the pdc role is down error 1355 To find PDC emulator, at the command line 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 /syncfro
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers
Error 1355 Server 2012
or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server
Dcdiag Error 1355
Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: dcgetdcname(time_server) call failed error 1355 Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Domain Controller DCdiag error - A Global Catalog Server could not be located up vote 3 down vote favorite 1 I've https://social.technet.microsoft.com/Forums/en-US/b4febe07-bff1-4e8d-a9c7-9a1fb1cc262e/fsmo-roles?forum=winserverDS set up a replica DC in a remote location. It's connected to the main site through a VPN connection. DCdiag passes on the primary DC, but I get the following error on the replica DC: Running enterprise tests on : mydomain.co.uk Starting test: LocatorCheck Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355 A Global Catalog Server could not be located - All GC's are down. Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355 A Primary Domain Controller could not be located. The server holding the PDC http://serverfault.com/questions/370314/domain-controller-dcdiag-error-a-global-catalog-server-could-not-be-located role is down. ......................... mydomain.co.uk failed test LocatorCheck Is it giving this error just because it is not the global catalogue server, or is there some connectivity issue where it does not think there is one at all, as the error seems to imply? If so, it seems odd, as all other tests were passed. What do I do about this? windows-server-2008-r2 domain-controller active-directory share|improve this question asked Mar 16 '12 at 2:35 paradroid 62931022 How's DNS set up on the replica? –Shane Madden♦ Mar 16 '12 at 2:58 @ShaneMadden: It was set up through netdom join. I assumed that was all that was needed. The DNS entries appear to have been replicated, apart from the DCs themselves (the original DC appears on both DNS databases, but the replica only appears through dig on the original, but with two entries, one being an out-of-date address). –paradroid Mar 16 '12 at 3:24 1 Are you in some kind of recovery scenario? The server is doing SRV record lookups to try and find the server holding the PDC Emulator FSMO role as well as looking for a Global Catalog server. I believe Shane was referring to the DNS client settings on the NIC of the remote server. –SpacemanSpiff Mar 16 '12 at 3:42 @SpacemanSpiff: I corrected the DNS discrepency I mentioned above, but I still get the error. No, it's just a new replica, not a
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 http://blog.shiraj.com/2009/09/dcgetdcnametime_server-call-failed-error-1355/ domain is as follows. Open Registry Editor (regedit.exe) 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 the local computer is marked as a reliable time 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 must call failed error 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 2015 Januar