Dcgetdcname Time Server Error 1355
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums Ask a question Quick access Forums home Browse forums users FAQ Search
Dcgetdcname(pdc_required) Call Failed Error 1355
related threads Remove From My Forums Answered by: Server error 1355 server 2012 Failed FSMO Test Windows Server > Directory Services Question 0 Sign in to vote Hello dcdiag failed test locatorcheck Thanks in advance for your help! So around early afternoon today, we lost the ability to login to the domain controller. dcdiag /test:fsmocheck gives
Dcdiag Error 1355
me the following: Starting test: fsmo check 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. Warning: DCGetDCName (KDC_required) call failed,
The Server Holding The Pdc Role Is Down
error 1355 A KDC could not be located - all the KDCs are down.
‘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: Advertising Warning: Server-Name is not dcdiag test advertising as a time server. ......................... Server-Name failed test Advertising Running enterprise tests on : PeteNetLive.com Starting test: Intersite ......................... PeteNetLive.com passed test Intersite 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. ......................... PeteNetLive.com failed test FsmoCheck Solution Note: Any one of the things below can https://social.technet.microsoft.com/Forums/windowsserver/en-US/744fb385-e8a8-402d-8053-9cf0496de13c/server-failed-fsmo-test?forum=winserverDS 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 a reliable external source. Windows - Setting Domain Time 3. If you have got this far, http://www.petenetlive.com/KB/Article/0000705 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; HKLM > System > CurrentControlSet > services > W32Time > Time Providers > NtpServer Make sure the Enabled value is set to 1 (one). 7. If the problem persists, on the PDC Emulator
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 https://www.experts-exchange.com/questions/25094646/Warning-DcGetDcName-TIME-SERVER-call-failed-error-1355.html 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 error 1355 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 dcgetdcname time server 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 byAwinish The e