Dcdiag 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
Warning Dcgetdcname Time_server Call Failed Error 1355
got thid issue when runing DCDIAG, any helps please Starting test: FsmoCheck fatal error dsgetdcname call failed error 1355 Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355 A Primary Domain Controller could not be located. The server holding the dsgetdcname call failed error 1355 the locator could not find the server PDC 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,
Dcgetdcname(gc_server_required) Call Failed Error 1355
error 135 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
Dcgetdcname(pdc_required) Call Failed Error 1355
the PDC emulator) 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
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the dclocator call failed with error 1355 workings and policies of this site About Us Learn more about
Dcdiag Failed Test Locatorcheck
Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions the server holding the pdc role is down error 1355 Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's https://social.technet.microsoft.com/Forums/en-US/b4febe07-bff1-4e8d-a9c7-9a1fb1cc262e/fsmo-roles?forum=winserverDS how it works: 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 set up a replica DC in a remote location. It's connected to the main site through a http://serverfault.com/questions/370314/domain-controller-dcdiag-error-a-global-catalog-server-could-not-be-located 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 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
Off on What to do when the Domain Controller Can't find its domain! PROBLEM: Users unable to login to the domain - DCs http://www.shofkom.com/2009/03/10/what-to-do-when-the-domain-controller-cant-find-its-domain/ not replicating RESOLUTION: => Set the RPC Locator service to Automatic and http://www.petenetlive.com/KB/Article/0000705 started on the PDC. => Still DCdiag gave errors of 1355. => Ran dcdiag on both PDC and BDC - both showed problems with sysvol and netlogon shares => Checked and found that both servers did not have sysvol and netlogon shared => Found that the SYSVOL was shared error 1355 as SYSVOLa - unshared it as it looked like manually shared. => Checked the PDC server and found that the Policies and Scripts were under the NTFRS-PRE-Existing folder => Stopped FRS Service on the BDC and PDC servers => Backed the policies and scripts from ntfrs-pre-existing folders to a folder on the desktop on PDC => Copied it on to the call failed error SYSVOL\sysvol folder => Started the FRS Service only on PDC => The sysvol and netlogon shares did not get created. => Stopped FRS Service again on PDC => On registry modified the following : HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup Burflags value to d4 => Started the FRS service on PDC => Got Event id : 13516 NTFRS on the PDC File replication service event log => On the BDC modified the registry : HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup Burflags value to d2 => Started FRS Service on BDC => Got Event id : 13516 NTFRS on the BDC File Replication service event log => Checked replication using repadmin /syncall - looks fine on both servers => Ran dcdiag /q on BDC and got no errors => Ran dcdiag /q on PDC and got one warning of 13508 and 13509 being reported on the eventlogs => Restarted FRS service on the PDC and reran dcdiag /q - got no errors now => All looks fine I researched the Event ID received from the following portion of a dcdiag on PDC: Starting test: FsmoCheck Warning: DcGetDcName(GC_SERVER_REQUIRED) call fa
‘A Good Time server could not be located' Home » Microsoft » Windows - Error ‘A Good Time server could not be located' KB ID 0000705 Dtd 06/11/12 Problem Seen when running dcdiag, Error(s): Starting test: Advertising Warning: Server-Name is not advertising as a 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) 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 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 Windows Time service and try to unregister again, then re-register. WARNING: After doing this, you will need to set the time service to get reliable time from an NTP External Server again. 5. Press Windows Key+R > regedit {enter} > Navigate to the following registry key; HKLM > System > CurrentControlSet > services > W32Time > Parameters Ensure th