Dcdiag Error 1355 Dcgetdcname
Contents |
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: dcgetdcname call failed error 1355 DCDIAG showing multiple errors for enterprise tests - error 1355
Dcdiag Error 1355 All Gc Are Down
Windows Server > Directory Services Question 0 Sign in to vote Hello there, Am hoping someone dcdiag failed test locatorcheck can help... On 1 of my 2008 R2 DCs (AV2) I'm seeing multiple errors for enterprise tests from DCDIAG (please see output below). The errors
All Gc Are Down Error 1355
are mainly 1355 and they sound quite serious ("A Primary Domain Controller could not be located", "The server holding the PDC role is down."). In Event Viewer on my AV2 server I'm also seeing errors 1202 (Active Directory Web Services) and 8016 (related to my Sophos anti-virus management console). These issues the server holding the pdc role is down error 1355 seemed to have cropped up after installing a bunch of Microsoft updates. Thanks in advance for any feedback. C:\Users\admin1.mydomain>netdom query fsmo Schema master FS1.mydomain.com Domain naming master FS1.mydomain.com PDC FS1.mydomain.com RID pool manager FS1.mydomain.com Infrastructure master FS1.mydomain.com The command completed successfully. C:\Users\admin1.mydomain> C:\Users\admin1.mydomain> C:\Users\admin1.mydomain>dcdiag Directory Server Diagnosis Performing initial setup: Trying to find home server... Home Server = AV2 * Identified AD Forest. Done gathering initial info. Doing initial required tests Testing server: Default-First-Site-Name\AV2 Starting test: Connectivity ......................... AV2 passed test Connectivity Doing primary tests Testing server: Default-First-Site-Name\AV2 Starting test: Advertising Warning: AV2 is not advertising as a time server. ......................... AV2 failed test Advertising Starting test: FrsEvent ......................... AV2 passed test FrsEvent Starting test: DFSREvent ......................... AV2 passed test DFSREvent Starting test: SysVolCheck ......................... AV2 passed test SysVolCheck Starting test: KccEvent .......
360 games PC games
Error 1355 Server 2012
Windows games Windows phone games Entertainment All Entertainment
Fatal Error:dsgetdcname
Movies & TV Music Business & Education Business Students & educators dcgetdcname(time_server) call failed error 1355 Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet https://social.technet.microsoft.com/Forums/en-US/54400c1c-d543-481d-8527-278587040a7e/dcdiag-showing-multiple-errors-for-enterprise-tests-error-1355?forum=winserverDS 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 https://support.microsoft.com/en-us/kb/958804 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
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 http://www.shofkom.com/2009/03/10/what-to-do-when-the-domain-controller-cant-find-its-domain/ 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 http://www.pcreview.co.uk/threads/warning-dcgetdcname-pdc_required-call-failed-error-1355.2167383/ 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 error 1355 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 dcdiag error 1355 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, error 1355 A Global Catalog Server could not be located -
3, 2005. zealousworks Guest I have an native Windows 2000 Active Directory domain with a number of remote sites, and I am trying to diagnose some Netlogon error messages appearing in the event log of the remote domain controllers: Event Type: Error Event Source: NETLOGON Event Category: None Event ID: 5719 Date: 03/10/2005 Time: 11:08:33 User: N/A Computer: SITE02AD01 Description: No Windows NT or Windows 2000 Domain Controller is available for domain WALKERS. The following error occurred: There are currently no logon servers available to service the logon request. Data: 0000: 5e 00 00 c0 ^..À Event Type: Error Event Source: NETLOGON Event Category: None Event ID: 3096 Date: 03/10/2005 Time: 15:55:20 User: N/A Computer: SITE02AD01 Description: The Windows NT domain controller for this domain could not be located. If I run 'dcdiag /v' on the domain controller, the following is listed for the FsmoCheck Starting test: FsmoCheck GC Name: \\site02dc01.walkers.co.uk Locator Flags: 0xe00001fc Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355 A Primary Domain Controller could not be located. The server holding the PDC role is down. Time Server Name: \\site02dc01.walkers.co.uk Locator Flags: 0xe00001fc Preferred Time Server Name: \\site02dc01.walkers.co.uk Locator Flags: 0xe00001fc KDC Name: \\site02dc01.walkers.co.uk Locator Flags: 0xe00001fc ......................... domain.co.uk failed test FsmoCheck But if I run 'netdom query fsmo', the following is reported: Schema owner site01ad01.walkers.co.uk Domain role owner site01ad01.walkers.co.uk PDC role site01ad02.walkers.co.uk RID pool manager site01ad02.walkers.co.uk Infrastructure owner site01ad02.walkers.co.uk The command completed successfully. Any suggestions appreciated! Regards, Andrew zealousworks, Oct 3, 2005 #1 Advertisements Paul Bergson Guest Has the sysvol share come online and/or is the netlogon service running? Check your event viewer. The second test is just telling you it knows the name of the roles holder, not that it can