Dcdiag Fsmo Check Error 1355
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 dcdiag fsmocheck failed error 1355 posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault dcdiag test fsmocheck 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
Dcdiag Error 1355 All Gc Are Down
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 favorite 1 I've set up
Dcgetdcname(gc_server_required) Call Failed Error 1355
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. The server holding the PDC role is all gc are down error 1355 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. No, it's just a new replica, not a recovery. I just checked th
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
The Server Holding The Pdc Role Is Down Error 1355
writeable directory The DC DC1 is advertising as a Key Distribution Center Warning: dcdiag failed test locatorcheck DC1 is not advertising as a time server. The DS DC1 is advertising as a GC. ......................... DC1 failed test warning dcgetdcname(time_server) call failed error 1355 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 http://serverfault.com/questions/370314/domain-controller-dcdiag-error-a-global-catalog-server-could-not-be-located 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 http://ben.goodacre.name/tech/Domain_Controller_is_not_advertising_as_a_time_server_Error_in_dcdiag_(Windows) 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 be used on Server 2008. If you received the error message: The service name is invalid earlier the Windows Time service is not even registered. Re-registering the W32time service can also fix some issues so perform these steps anyway: Re-registering the Windows Time Service Try:w32tm /resync /redisscover Check that the DC has the PDC role: net
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 http://clintboessen.blogspot.com/2013/11/the-server-holding-pdc-role-is-down.html DCDiag on any domain controller in the domain, all domain controllers complained the PDC role https://www.experts-exchange.com/questions/25094646/Warning-DcGetDcName-TIME-SERVER-call-failed-error-1355.html 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 error 1355 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 failed error 1355 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 netdom returned it successfully. Why are all domain controllers
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 Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Warning: DcGetDcName(TIME_SERVER) call failed, error 1355 Want to Advertise Here? Solved Warning: DcGetDcName(TIME_SERVER) call failed, error 1355 Posted on 2010-01-28 MS Legacy OS Active Directory Windows Server 2003 2 Verified Solutions 8 Comments 3,937 Views Last Modified: 2012-11-06 Running dcdiag on a windows 2003 native AD domain.. Simple, one domain, one forest, three domain controllers all of them GCs. Every AD server returns this error: DC1 is not advertising as a time server. And this: 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. I have done all of this: http://ben.goodacre.name/tech/Domain_Controller_is_not_advertising_as_a_time_server_Error_in_dcdiag_(Windows) Netdom query pdc runs fine on all of the servers, returns the correct pdc emulator. Everything seems to be fine except that error in dcdiag and Event ID: 14 is in one AD server's log multiple times: The time provider NtpClient was unable to find a domain controller to use as a time source. NtpClient will try again in 240 minutes. This server is on a different subnet than the other two. I just ran w32tm on the other AD server (non pdc emulator) and it returned 'the computer did not resync because no time data was available' and logged an event id: 14 in the system log. This one has me stumped.. any ideas how to fix this? I want to upgrade the domain to AD 2008, but am afraid to with this happening. 0 Question by:H2Omike Facebook Twitter LinkedIn Google LVL 24 Best Solution byAwinis