Fsmocheck 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 Test Windows Server > Directory Services dcgetdcname(gc_server_required) call failed error 1355 Question 0 Sign in to vote Hello Thanks in advance for your help! error 1355 server 2012 So around early afternoon today, we lost the ability to login to the domain controller. dcdiag /test:fsmocheck gives me dcdiag failed test locatorcheck 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, the server holding the pdc role is down error 1355 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.
Error 1355 All Gc's Are Down
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 lost the ability to login to the domain controller”. Any error message received? Please first check the following links: Error Messages Occur When Active Directory Users and Computers Snap-in Is Opened http://support.m
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
Dsgetdcname Call Failed Error 1355
Help Receive Real-Time Help Create a Freelance Project Hire for a fatal error:dsgetdcname call failed, error 1355 server 2012 Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products restart the ntfrs service BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > how solve "DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355" Want to Advertise Here? https://social.technet.microsoft.com/Forums/windowsserver/en-US/744fb385-e8a8-402d-8053-9cf0496de13c/server-failed-fsmo-test?forum=winserverDS Solved how solve "DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355" Posted on 2012-02-02 Active Directory Windows Server 2003 2 Verified Solutions 6 Comments 9,922 Views Last Modified: 2012-02-06 hello in attached document you can see result of "DCDIAG /v" (log-dcdiag.txt) in attached document you can see result of "dnslint /ad 127.0.0.1 /s 192.168.0.14 /v" (dnslint.txt) I have https://www.experts-exchange.com/questions/27568710/how-solve-DcGetDcName-GC-SERVER-REQUIRED-call-failed-error-1355.html make this too : netdom query fsmo and the result of this is : Schema owner dc-wnc1hnl0oyu.lci.local Domain role owner dc-wnc1hnl0oyu.lci.local PDC role dc-wnc1hnl0oyu.lci.local RID pool manager dc-wnc1hnl0oyu.lci.local Infrastructure owner dc-wnc1hnl0oyu.lci.local The command completed successfully. I have this problem after crash of my PDC I have forcer promot for give All role at my seconde DC but now I have this error "DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355" how can solved this ? thx dnslint.txt log-dcdiag.txt 0 Question by:thierry91 Facebook Twitter LinkedIn Google LVL 26 Best Solution byLeon Fester Verify that this server is a global catalog, run repadmin /options You should see at least "Current Options: IS_GC" If not, then following instructions from here http://support.microsoft.com/kb/313994 Go to Solution 6 Comments LVL 17 Overall: Level 17 Active Directory 12 Windows Server 200
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 https://www.experts-exchange.com/questions/25094646/Warning-DcGetDcName-TIME-SERVER-call-failed-error-1355.html 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,961 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 error 1355 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 call failed error 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 error related due to time sync issue. Please check port 123 tcp as well as UDP has been opened on DC for inbound & outbound connection in firewall. Please check below link & reply also enable debug Go to Solution 8 Comments Message Author Comment by:H2Omike2010-01-28 http://forums.techarena.in/active-directory/32759.htm This seems to have helped. Now when I run dcdiag /e the only error I get is DC1 is not advertising as a time server. DC1 is the pdc emulator, the other two AD servers are now sychronizing (either with the p