Fsmocheck Call Failed Error 1355
Contents |
360 games PC games dcdiag failed test locatorcheck Windows games Windows phone games Entertainment All Entertainment dcgetdcname(pdc_required) call failed, error 1355 Movies & TV Music Business & Education Business Students & educators
The Server Holding The Pdc Role Is Down Error 1355
Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet
Warning Dcgetdcname(time_server) Call Failed Error 1355
Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Lumia All error 1355 server 2012 Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: FSMO Roles Windows Server > Directory Services Question 0 Sign in to vote Hi I
All Gc Are Down Error 1355
got thid issue when runing DCDIAG, any helps please Starting test: FsmoCheck dsgetdcname call failed, error 1355 Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355 A Primary Domain Controller could not be located. The server holding the fatal error:dsgetdcname call failed, error 1355 server 2012 PDC role is down. 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 https://support.microsoft.com/en-us/kb/958804 failed, error 135 5 A Good Time Server could not be located. Thursday, October 04, 2012 5:06 PM Reply | Quote Answers 0 Sign in to vote Hi, "The server holding the PDC role is down" On the server holding the PDC emulator role, check whether the Windows Time service is started. Also check on the server on which the dcdiag was run..(if it is https://social.technet.microsoft.com/Forums/en-US/b4febe07-bff1-4e8d-a9c7-9a1fb1cc262e/fsmo-roles?forum=winserverDS not the PDC emulator) To find PDC emulator, at the command line on a DC run the following Netdom query fsmo To check the status of the Windows Time service Go to Administrative Tools -> Services Ensure that the Windows Time service is set to automatic start up and that it is started. Reboot the server then run the dcdiag test again.SelloD Proposed as answer by Cicely FengModerator Friday, October 05, 2012 2:45 AM Marked as answer by Cicely FengModerator Monday, October 15, 2012 7:27 AM Thursday, October 04, 2012 8:04 PM Reply | Quote 0 Sign in to vote Hi, It seems the "Authorative Time server" is not configured or down. Please run "netdom query dc" command and verify the PDC emulator role owner DC name and ensure that it is online and Windows Time service is in started state. AlsoPDC role owner in forest root domain should be configured as an authorative time server other DCs should sync with PDC and domain members should sync with DCs. Run following commands: On PDC emulator: w32tm /config /manualpeerlist:time.windows.com,0×1 /syncfromflags:manual /reliable:yes /update net stop w32time & net start w32time & w32tm /resync /rediscover On Non -PD
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 http://serverfault.com/questions/370314/domain-controller-dcdiag-error-a-global-catalog-server-could-not-be-located more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered http://www.shofkom.com/2009/03/10/what-to-do-when-the-domain-controller-cant-find-its-domain/ 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 Domain Controller DCdiag error - A Global Catalog Server could not be located up error 1355 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 A call failed, error 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:42 @Spa
Off on What to do when the Domain Controller Can't find its domain! PROBLEM: Users unable to login to the domain - DCs not replicating RESOLUTION: => Set the RPC Locator service to Automatic and started on the PDC. => Still DCdiag gave errors of 1355. => Ran dcdiag on both PDC and BDC - both showed problems with sysvol and netlogon shares => Checked and found that both servers did not have sysvol and netlogon shared => Found that the SYSVOL was shared as SYSVOLa - unshared it as it looked like manually shared. => Checked the PDC server and found that the Policies and Scripts were under the NTFRS-PRE-Existing folder => Stopped FRS Service on the BDC and PDC servers => Backed the policies and scripts from ntfrs-pre-existing folders to a folder on the desktop on PDC => Copied it on to the SYSVOL\sysvol folder => Started the FRS Service only on PDC => The sysvol and netlogon shares did not get created. => Stopped FRS Service again on PDC => On registry modified the following : HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup Burflags value to d4 => Started the FRS service on PDC => Got Event id : 13516 NTFRS on the PDC File replication service event log => On the BDC modified the registry : HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup Burflags value to d2 => Started FRS Service on BDC => Got Event id : 13516 NTFRS on the BDC File Replication service event log => Checked replication using repadmin /syncall - looks fine on both servers => Ran dcdiag /q on BDC and got no errors => Ran dcdiag /q on PDC and got one warning of 13508 and 13509 being reported on the eventlogs => Restarted FRS service on the PDC and reran dcdiag /q - got no errors now => All looks fine I researched the Event ID received from the following portion of a dcdiag on PDC: Starting test: FsmoCheck Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, e