Error 1355 Dcdiag
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
Erreur 1355 Dcdiag
more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges dcdiag failed test locatorcheck Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a
Dcdiag Error 1355 Gc Server Required
minute: Sign up Here's how 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 dcdiag error 1355 pdc required 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: 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 dcdiag fsmocheck 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 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:4
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
Dcdiag Error 1355 Global Catalog
controller (eagle2, server 2003). We have had a new domain controller (eagle3, server dcdiag error 1355 dcgetdcname 2008) in place for the entire school year and has been working fine running AD, DNS, DHCP, and file services.
Dcdiag Error 1355 All Gc Are Down
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 http://serverfault.com/questions/370314/domain-controller-dcdiag-error-a-global-catalog-server-could-not-be-located 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 start troubleshooting this, Google didn't really help so https://community.spiceworks.com/topic/318178-dcdiag-failed-error-1355-troubleshooting 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
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 http://clintboessen.blogspot.com/2013/11/the-server-holding-pdc-role-is-down.html 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 http://ben.goodacre.name/tech/Domain_Controller_is_not_advertising_as_a_time_server_Error_in_dcdiag_(Windows) 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 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 dcdiag error 1355 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 u
can appear: Starting test: Advertising The DC DC1 is advertising itself as a DC and having a DS. The DC DC1 is advertising as an LDAP server The DC DC1 is advertising as having a writeable directory The DC DC1 is advertising as a Key Distribution Center Warning: DC1 is not advertising as a time server. The DS DC1 is advertising as a GC. ......................... DC1 failed test Advertisingche The exact command run to produce this test is: dcdiag /v /test:advertising FSMO Check Another error can appear within a different check in dcdiag: Starting test: FsmoCheck 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. The exact command run to produce this test is: dcdiag /test:fsmocheck Cause The dcdiag tool detects that the time service is either not running or is running but not announcing itself as a reliable time server. Resolution Try each of these solutions one step at a time, re-testing after completing each step until the problem is resolved. Ensure the Windows Time service is running. On a DC it is part of the core AD functonality and should be runing even if synchronised time is not essential.net start w32time Restart the Windows time servicenet stop w32time && net start w32time Check that Network problems are not stopping NTP form functioning. Note that Windows clients do not synchronise with the DCs via NTP, this only tests the ability for DC themselves to check an external time source:w32tm /stripchart /computer:time.windows.com /samples:2 /dataonlyError 0x800705B4 is a network timeout on the port - 123. Time.winfows.com should be replaced with the external time server you are using for a more complete test. Try: netdiag /fix Netdiag is part of Windows Server 2003 Service Pack 1 Support Tools. This can also b