Dcdiag Error 1355 Gc_server_required
Contents |
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 or posting dcdiag error 1355 all gc are down ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a
Dcdiag Fsmocheck Failed Error 1355
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
Dcdiag Failed Test Locatorcheck
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
All Gc Are Down Error 1355
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 role is down. ......................... mydomain.co.uk failed the server holding the pdc role is down error 1355 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 recovery. I just checked the DNC client settings. They original DC is
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 Full Time Job error 1355 server 2012 Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts fatal error:dsgetdcname Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > how solve "DcGetDcName(GC_SERVER_REQUIRED) call failed, dcgetdcname(time_server) call failed error 1355 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 9,798 Views Last Modified: 2012-02-06 hello in http://serverfault.com/questions/370314/domain-controller-dcdiag-error-a-global-catalog-server-could-not-be-located 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 dc-wnc1hnl0oyu.lci.local PDC role https://www.experts-exchange.com/questions/27568710/how-solve-DcGetDcName-GC-SERVER-REQUIRED-call-failed-error-1355.html 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 Message Assisted Solution by:Leon Fester2012-02-03 Some errors from your DCDIAG can be fixed by running the following commands on your D
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 http://www.shofkom.com/2009/03/10/what-to-do-when-the-domain-controller-cant-find-its-domain/ RESOLUTION: => Set the RPC Locator service to Automatic and started on http://www.vistax64.com/sbs-server/254125-cannot-locate-global-catalog-server-error-1355-dcdiag.html 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 - error 1355 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 SYSVOL\sysvol folder => Started the dcdiag error 1355 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 failed, error 1355 A Global Catalog Server could not be
locate Global Catalog server error 1355 from dcdiag Cannot locate Global Catalog server error 1355 from dcdiag New 15 Sep 2009 #1 George Guest Cannot locate Global Catalog server error 1355 from dcdiag Hello, I'm running Windows SBS 2003 SP2. This is the only server up and running in my domain. This morning users reported slow login times. The application log shows two errors every 5 minutes: event ID 1006 Windows cannot bind to mydomain domain. (Local Error). Group Policy processing aborted. and event ID 1030 Windows cannot query for the list of Group Policy objects. Check the event log for possible messages previously logged by the policy engine that describes the reason for this. I also have this error once in the system log: event ID 16645 The maximum account identifier allocated to this domain controller has been assigned. The domain controller has failed to obtain a new identifier pool. A possible reason for this is that the domain controller has been unable to contact the master domain controller. Account creation on this controller will fail until a new pool has been allocated. There may be network or connectivity problems in the domain, or the master domain controller may be offline or missing from the domain. Verify that the master domain controller is running and connected to the domain. At 4:30am my time I had the 16645, the other two started appearing two minutes later and are still appearing every 5 minutes. I ran dcdiag and saw this in the output: 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(PDC_REQUIRED) call failed, error 1355 A Primary Domain Controller could not be located. The server holding the 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(KDC_REQUIRED) call failed, error 1355 A KDC could not be located - All the KDCs are down. ......................... mydomain failed test FsmoCheck I am now wondering what course of action I should take