Dcdiag 1355 Error
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 erreur 1355 dcdiag developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _
Dcdiag Failed Test Locatorcheck
Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how
Dcdiag Error 1355 Gc Server Required
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
Dcdiag Error 1355 Pdc Required
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: 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. dcdiag fsmocheck failed error 1355 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 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.
Migration Upgrade Intranet Upgrade current intranet to a new platform. Tweaks and minimal new development. Establish long term system management. Windows 7 Migration April 2014 approaches and it's time for the company PCs to be either replaced or OS upgraded from Windows XP to dcdiag error 1355 global catalog Windows 7 Pro. IN THIS DISCUSSION Join the Community! Creating your account only takes a few dcdiag error 1355 dcgetdcname minutes. Join Now Hey all, A little background info: We have a customer school district that has been having some issues with an old domain dcdiag error 1355 all gc are down controller (eagle2, server 2003). We have had a new domain controller (eagle3, server 2008) in place for the entire school year and has been working fine running AD, DNS, DHCP, and file services. Some things like group policy were still being handled http://serverfault.com/questions/370314/domain-controller-dcdiag-error-a-global-catalog-server-could-not-be-located by eagle2 so I decided I would start moving all of its responsibilities onto Eagle3 in an effort to remove eagle2 completely. After I moved operations master roles from eagle2 to eagle3 I started to experience some problems. eagle3 is unable to do anything with active directory "Naming information can not be located for the following reason: The server is not operational". eagle2 still seems to be operational though. I've looked at DNS, everything SEEMS to be okay there. I'm just not sure where to https://community.spiceworks.com/topic/318178-dcdiag-failed-error-1355-troubleshooting start troubleshooting this, Google didn't really help so hopefully you guys have some ideas for me :) A lot of the errors I see in the event log point to global catalog server not being reachable. Attached is the output from dcdiag. Thanks in advance! Jordan dcdiag.txt (3.02 KB) Reply Subscribe View Best Answer RELATED TOPICS: Let's have a look at the DC, running DCDIAG gives me the following error: DCDIAG error DCDiag Errors - Any Advice   10 Replies Mace OP Sosipater Mar 27, 2013 at 2:13 UTC Is eagle3 setup as a GC? 0 Mace OP Helpful Post Jay6111 Mar 27, 2013 at 2:16 UTC Is the Windows firewall turned on, on eagle3? It's also having trouble locating a time server, do you have an internal or external time server setup? Run the following from eagle 2 and post the file up for review. dcdiag.exe /e /f:"C:\dcdiag.txt" -Jay 0 Cayenne OP Jordan W Mar 27, 2013 at 2:29 UTC Thanks guys, I'm not sure about the GC. The tech that works here is moving on so I'm just trying to clean things up for the next guy. I'm also not sure about the time server, we have one at our main office I would like to use but I'm not sure where to set it up. Attached is the dcdiag from eagle2 dcdiag.txt (18.3 KB) 0 Cayenne OP Jordan W Mar 27, 2013
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 https://www.experts-exchange.com/questions/27568710/how-solve-DcGetDcName-GC-SERVER-REQUIRED-call-failed-error-1355.html Hire for a Full Time Job Ways to Get Help Expand Search http://www.shofkom.com/2009/03/10/what-to-do-when-the-domain-controller-cant-find-its-domain/ Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > 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 error 1355 2003 2 Verified Solutions 6 Comments 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 dcdiag error 1355 dc-wnc1hnl0oyu.lci.local Domain role owner 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.mic
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 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. => 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 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