Dcdiag Error 1355
Contents |
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: DCDIAG showing multiple dcdiag error 1355 all gc are down errors for enterprise tests - error 1355 Windows Server > Directory
Erreur 1355 Dcdiag
Services Question 0 Sign in to vote Hello there, Am hoping someone can help... On 1 dcdiag failed test locatorcheck of my 2008 R2 DCs (AV2) I'm seeing multiple errors for enterprise tests from DCDIAG (please see output below). The errors are mainly 1355 and they sound dcdiag error 1355 gc server required quite serious ("A Primary Domain Controller could not be located", "The server holding the PDC role is down."). In Event Viewer on my AV2 server I'm also seeing errors 1202 (Active Directory Web Services) and 8016 (related to my Sophos anti-virus management console). These issues seemed to have cropped up after installing a bunch
Dcdiag Error 1355 Pdc Required
of Microsoft updates. Thanks in advance for any feedback. C:\Users\admin1.mydomain>netdom query fsmo Schema master FS1.mydomain.com Domain naming master FS1.mydomain.com PDC FS1.mydomain.com RID pool manager FS1.mydomain.com Infrastructure master FS1.mydomain.com The command completed successfully. C:\Users\admin1.mydomain> C:\Users\admin1.mydomain> C:\Users\admin1.mydomain>dcdiag Directory Server Diagnosis Performing initial setup: Trying to find home server... Home Server = AV2 * Identified AD Forest. Done gathering initial info. Doing initial required tests Testing server: Default-First-Site-Name\AV2 Starting test: Connectivity ......................... AV2 passed test Connectivity Doing primary tests Testing server: Default-First-Site-Name\AV2 Starting test: Advertising Warning: AV2 is not advertising as a time server. ......................... AV2 failed test Advertising Starting test: FrsEvent ......................... AV2 passed test FrsEvent Starting test: DFSREvent ......................... AV2 passed test DFSREvent Starting test: SysVolCheck ......................... AV2 passed test SysVolCheck Starting test: KccEvent ......................... AV2 passed test KccEvent Starting test: KnowsOfRoleHolders ......................... AV2 passed test KnowsOfRoleHolders Starting test
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 dcdiag fsmocheck failed error 1355 domain controller in the domain, all domain controllers complained the PDC role is down. This dcdiag error 1355 global catalog 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
Dcdiag Error 1355 Dcgetdcname
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 https://social.technet.microsoft.com/Forums/en-US/54400c1c-d543-481d-8527-278587040a7e/dcdiag-showing-multiple-errors-for-enterprise-tests-error-1355?forum=winserverDS 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 http://clintboessen.blogspot.com/2013/11/the-server-holding-pdc-role-is-down.html 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 netdom returned it successfully. Why are all domain controllers complaining the PDC role is down when doing a DCDiag? The Resolution I
Update Deployment You know Java: It's always being updated to fix security flaws! Migrating from Exchage 2007 to Office 365 Project to move from onsite Microsoft Exchange 2007 server to Office 365 cloud based email system. https://community.spiceworks.com/topic/318178-dcdiag-failed-error-1355-troubleshooting Active Directory Migration Migrate client network from NT4 to Active Directory domain. IN THIS DISCUSSION Join the Community! Creating your account only takes a few 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 controller (eagle2, server 2003). We have had a new domain controller (eagle3, server 2008) in place for the entire school year and has been error 1355 working fine running AD, DNS, DHCP, and file services. Some things like group policy were still being handled 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: dcdiag error 1355 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 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