Fsmo Check Failed Error 1355
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Server Failed FSMO dcgetdcname(gc_server_required) call failed error 1355 Test Windows Server > Directory Services Question 0 Sign in to vote dsgetdcname call failed error 1355 Hello Thanks in advance for your help! So around early afternoon today, we lost the ability to login fatal error:dsgetdcname call failed, error 1355 server 2012 to the domain controller. dcdiag /test:fsmocheck gives me the following: Starting test: fsmo check Warning: DCGetDcName (TIME_SERVER) call failed, error 1355 A Time Server could not be located. The server all gc are down error 1355 holding the PDC role is down. Warning: DCGetDcName (GOOD_TIME_SERVER_PREFERRED) call failed, error 1355 A good time server could not be located. Warning: DCGetDCName (KDC_required) call failed, error 1355 A KDC could not be located - all the KDCs are down.
Dcdiag Failed Test Locatorcheck
Directory is not working correctly. Can anyone shed some insight on how to resolve this issue? Thanks again! Reezie Thursday, June 09, 2011 12:47 AM Reply | Quote Answers 0 Sign in to vote There can be two reason for this either Sysvol/Netlogon is missing or windows time service is not started. configure authoritative time server http://support.microsoft.com/kb/816042 Post below result on skydrive ONLY dcdiag /v/c/d/e/s:dcname > c:\dcdiag.log ipconfig /all from the DC http://explore.live.com/windows-live-skydrive I would like to see below info of your environments to get the complete picture. -No of forest & domain -No of domain controller, their OS version & service pack level -No of sites & connectivity bandwidth b/w them -DFL/FFL level. Regards Awinish Vishwakarma| CHECK MY BLOG Disclaimer: This posting is provided AS-IS with no warranties or guarantees and confers no rights. Marked as answer by Nina Liu - MSFTModerator Monday, June 20, 2011 9:33 AM Thursday, June 09, 2011 4:10 AM Reply | Quote Moderator 0 Sign in to vote Hi, Besides others asked, please also clarify the current situation, like “we
‘A Good Time server could not be located' Home » Microsoft » Windows - Error ‘A Good Time server could not be located' KB ID 0000705 Dtd 06/11/12 Problem Seen when running dcdiag, Error(s): Starting test:
The Server Holding The Pdc Role Is Down Error 1355
Advertising Warning: Server-Name is not advertising as a time server. ......................... Server-Name failed test dsgetdcname failed Advertising Running enterprise tests on : PeteNetLive.com Starting test: Intersite ......................... PeteNetLive.com passed test Intersite Starting test: FsmoCheck Warning: DcGetDcName(TIME_SERVER) call error 1355 server 2008 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. ......................... PeteNetLive.com failed https://social.technet.microsoft.com/Forums/windowsserver/en-US/744fb385-e8a8-402d-8053-9cf0496de13c/server-failed-fsmo-test?forum=winserverDS test FsmoCheck Solution Note: Any one of the things below can cause this problem, I suggest you retry running dcdiag after each step until it runs without error. 1. In a windows domain, clients normally get their time from the domain controller that holds the PDC Emulator role. Locate that server and log on. Locate your FSMO Role Servers 2. Now configure your PDC emulator to get its time from http://www.petenetlive.com/KB/Article/0000705 a reliable external source. Windows - Setting Domain Time 3. If you have got this far, then should already have the windows time service running, check! 4. From command line, remove and reinstall the Windows time service with the following two commands. w32tm /unregister
w32tm /register Note: It's not unusual to see the following error after you issue a 'w32tm /unregister' command, Error The following error occurred: Access is denied (0x80070005) If this happens don't panic, open the services console (Press F5) and the Windows Time Service may have disappeared (if so re-register it). If not manually stop the Windows Time service and try to unregister again, then re-register. WARNING: After doing this, you will need to set the time service to get reliable time from an NTP External Server again. 5. Press Windows Key+R > regedit {enter} > Navigate to the following registry key; HKLM > System > CurrentControlSet > services > W32Time > Parameters Ensure the Type value it set to NTP, the restart the Windows time service and check again. 5. Whilst still in the registry editor navigate to; HKLM > System > CurrentControlSet > services > W32Time > Config Set the AnnounceFlags value to 5. 6. Whilst still in the registry editor navigate to;
single Active Directory domain with a single forest. This domain has a central site and approximately15 remote branch sites in a hub http://clintboessen.blogspot.com/2013/11/the-server-holding-pdc-role-is-down.html and spoke type 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 http://serverfault.com/questions/34354/how-do-you-repair-active-directory-after-a-partially-renamed-domain-controller 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 error 1355 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 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 failed error 1355 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 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 interva
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 ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ 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 it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top How do you repair active directory after a partially renamed domain controller? up vote 2 down vote favorite I have a 2008 Server (only DC in the domain) which crashed during a rename. As a result it left the system half renamed. The computer name had been changed to DC1 but there were still many references to DC2 (the old computer name) such as in DNS and Active directory. As a result the Netlogon service will not start and Active directory cannot be accessed. After about 8 hours of hard work, I manged to make some progress by manualy editing DNS records and update Active Directory records using ADSIEdit. When i run netdiag i get the following output... Computer Name: DC1 DNS Host Name: dc1.school.local System info : Windows Server (R) 2008 Standard (Build 6002) Processor : x86 Family 6 Model 15 Stepping 11, GenuineIntel Hotfixes : none detected Netcard queries test . . . . . . . : Passed [WARNING] The net card 'RAS Async Adapter' may not be working because it has not received any packets. GetStats failed for 'isatap.{A9F5A39A-FD61-44C4-BE9F-1E4BD5A3B546}'. [ERROR_GEN_FAILURE] Per interface results: Adapter : Local Area Connection Netcard queries test . . . : Passed Host Name. . . . . . . . . : dc1 IP Address . . . . . . . . : 192.168.1.3