Dcgetdcname Error 1355
Contents |
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a fatal error dsgetdcname Full Time Job Ways to Get Help Expand Search Submit Close Search Login
Error 1355 All Gc Are Down
Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions >
Dcgetdcname Call Failed 1355
how solve "DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355" Want to Advertise Here? Solved how solve "DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355" Posted on 2012-02-02 Active Directory Windows Server 2003 2 Verified Solutions 6 Comments
Dcdiag Failed Test Locatorcheck
9,798 Views Last Modified: 2012-02-06 hello in attached document you can see result of "DCDIAG /v" (log-dcdiag.txt) in attached document you can see result of "dnslint /ad 127.0.0.1 /s 192.168.0.14 /v" (dnslint.txt) I have make this too : netdom query fsmo and the result of this is : Schema owner dc-wnc1hnl0oyu.lci.local Domain role owner the server holding the pdc role is down error 1355 dc-wnc1hnl0oyu.lci.local PDC role dc-wnc1hnl0oyu.lci.local RID pool manager dc-wnc1hnl0oyu.lci.local Infrastructure owner dc-wnc1hnl0oyu.lci.local The command completed successfully. I have this problem after crash of my PDC I have forcer promot for give All role at my seconde DC but now I have this error "DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355" how can solved this ? thx dnslint.txt log-dcdiag.txt 0 Question by:thierry91 Facebook Twitter LinkedIn Google LVL 26 Best Solution byLeon Fester Verify that this server is a global catalog, run repadmin /options You should see at least "Current Options: IS_GC" If not, then following instructions from here http://support.microsoft.com/kb/313994 Go to Solution 6 Comments LVL 17 Overall: Level 17 Active Directory 12 Windows Server 2003 9 Message Expert Comment by:Premkumar Yogeswaran2012-02-03 I member checked a blog for this issue, which helped my friend.... http://blog.shiraj.com/index.php/2009/09/dcgetdcnametime_server-call-failed-error-1355/ Check this HTH... regards, Prem 0 LVL 10 Overall: Level 10 Active Directory 5 Windows Server 2003 4 Message Expert Comment by:jmanishbabu2012-02-03 Check this http://support.microsoft.com/kb/316790 Also this http://www.experts-exchange.com/Software/Server_Software/File_Servers/Active_Directory/Q_23970181.html 0 LVL 26 Overall: Level 26 Windows Server 2003 17 Active Directory 15
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 error 1355 server 2012 site About Us Learn more about Stack Overflow the company Business Learn dcgetdcname(time_server) call failed error 1355 more about hiring developers 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: Anybody can ask a question Anybody can https://www.experts-exchange.com/questions/27568710/how-solve-DcGetDcName-GC-SERVER-REQUIRED-call-failed-error-1355.html 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 VPN connection. DCdiag passes on the primary DC, but I get the following error on http://serverfault.com/questions/370314/domain-controller-dcdiag-error-a-global-catalog-server-could-not-be-located 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 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
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 the RPC Locator http://www.shofkom.com/2009/03/10/what-to-do-when-the-domain-controller-cant-find-its-domain/ service to Automatic and started on the PDC. => Still DCdiag gave errors of http://clintboessen.blogspot.com/2013/11/the-server-holding-pdc-role-is-down.html 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. => Checked the PDC server error 1355 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 did not get created. => Stopped FRS Service again dcgetdcname error 1355 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 the PDC role is down. http://technet2.microsoft.com/windowsserver/en/library/ce8890cf-ef46-4931-8e4a-2fc5b4ddb0471033.mspx?mfr=true http://technet2.microsoft.com/windowsserver/en/library/b43a025f-cce2-4c82-b3ea-3b95d482db3a1033.mspx?mfr=true At first I believed the problem to be related to us
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 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 request went to the PDC emulator to validate the users password has changed - hence the PDC emulator is in working order. Also querying the PDC emulator with ne