Dcdiag Dcgetdcname Error 1355
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeWindows 10Windows 10 MobilePrevious versionsMDOPSurfaceSurface HubLibraryForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: A Global Catalog Server could not be located dcgetdcname(pdc_required) 1355 - All GC's are down. Windows Server > Directory Services Question 0 Sign
Dcgetdcname Call Failed Error 1355
in to vote Im all out of ideas. I have two DC's that both fail DCDIAG with the following
Dcdiag Error 1355 All Gc Are Down
adn my exchange services wont come online due to this. please help!Starting test: FsmoCheck Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355 A Global Catalog Server could not be located - All GC's
Dcdiag Failed Test Locatorcheck
are down. PDC Name: \\xx.xxxxx.xxxx ( servername and domain are correct) Locator Flags: 0xe00001fd 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. Warning: DcGetDcName(KDC_REQUIRED) call failed, error 1355 A KDC could not be located - all gc are down error 1355 All the KDCs are down.Both Dc's are GC's and users can log on to either DC. Sunday, November 16, 2008 9:52 PM Reply | Quote Answers 2 Sign in to vote Some troubleshooting ideas:0. Check if the DCs can resolve each other using their DNSHostName. If not, this indicates some DNS misconfiguration -- you need to fix that first.1. Check if the both the DCs are pointing to the same DNS server (or DNS servers that are replica of each other). Run: "ipconfig /all" and check its output. If not, correct the DNS client settings and run dcdiag after sometime.2. Check if dynamic updates are "turned on" on the DNS server.3. Try re-registering the DCs SRV records by either restarting netlogon service or by running the following command: nltest.exe /dsregdnsHTHSwami Marked as answer by Joson ZhouModerator Monday, November 24, 2008 10:16 AM Monday, November 17, 2008 6:07 PM Reply | Quote All replies 0 Sign in to vote Try removing and adding back the GCs through the AD Sites and Services snap-in. Open Active directory Sites and Services and then double-click sitename, double-click Servers, click
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 the server holding the pdc role is down error 1355 About Us Learn more about Stack Overflow the company Business Learn more about error 1355 server 2012 hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is dcdiag error 1355 a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The https://social.technet.microsoft.com/Forums/windows/en-US/a28c7d65-6591-4d61-81ba-b9cfe08ec734/a-global-catalog-server-could-not-be-located-all-gcs-are-down?forum=winserverDS 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 VPN connection. DCdiag passes on the primary DC, but I get the following error on the replica DC: http://serverfault.com/questions/370314/domain-controller-dcdiag-error-a-global-catalog-server-could-not-be-located 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 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
Off on What to do when the Domain Controller Can't find its domain! PROBLEM: Users unable to login to the domain - DCs not replicating RESOLUTION: => Set http://www.shofkom.com/2009/03/10/what-to-do-when-the-domain-controller-cant-find-its-domain/ the RPC Locator service to Automatic and 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 as SYSVOLa - unshared it as it looked like manually shared. error 1355 => 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 SYSVOL\sysvol folder => Started the FRS Service only on PDC => The sysvol and netlogon shares dcdiag error 1355 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 failed, error 1355 A Global Catalog Server could not be located - All GC's are down. Warning: DcGetDcName(TIME_SERVER) call failed, error 1355 A Time Server could not be located. The server holding th