Fatal Error Dsgetdcname Error 1355
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeOnline20132010Other VersionsRelated ProductsLibraryForumsGallery Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Fatal Error:DsGetDcName (servername) call failed, error 1355 The Locator could not fatal error:dsgetdcname call failed, error 1355 server 2012 find the server. Windows Server > Directory Services Question 0 Sign in fatal error dsgetdcname call failed error 1722 to vote What acttully happen ya..? Tuesday, November 16, 2010 4:57 AM Reply | Quote Answers 0 Sign in dcgetdcname(gc_server_required) call failed error 1355 to vote Hi It appears that your sites are not setup correctly or you have added new IP subnets that are not specified in current Sites. You will need to all gc are down error 1355 identify the client PCs in your netlogon.log and make sure that you have defined them in the correct site in your Active Directory Sites and Services http://technet.microsoft.com/en-us/library/cc728152(WS.10).aspx The link has steps for creating sites if you dont have them already. Regards Herbert, Regards zizebra http://auction.joyoustimes.net Marked as answer by Nina Liu - MSFTModerator Thursday, November 25, 2010 2:05 PM Tuesday, November 16,
Restart The Ntfrs Service
2010 9:28 AM Reply | Quote 0 Sign in to vote Hello, 2. the other ipconfig /all are missing, especially from the problem machines. 3. Think also about upgrading to SP3 on the Windows XP machines. 4. 1054 can belong to DNS problems, so see 2. And 5807 is logged if AD sites and services doesn't contain all subnets.Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Marked as answer by Nina Liu - MSFTModerator Thursday, November 25, 2010 2:05 PM Tuesday, November 16, 2010 11:26 AM Reply | Quote 0 Sign in to vote Hi, Please help clarify the current problems. Is it logon issue or the Group Policy applying issue on XP? Please check the following support articles first: Event ID 1054 is logged in the Application log in Windows Server 2003 or in Windows XP Professional http://support.microsoft.com/kb/324174 You may receive event ID 5807 on a Windows Server 2003-based domain controller http://support.microsoft.com/kb/889031#top If the issue persists, please help gather the followin
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
Dcdiag Failed Test Locatorcheck
Time Job Ways to Get Help Expand Search Submit Close Search Login Join dsgetdcname failed 0x54b Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Active error 1355 server 2008 Directory cannot connect to domain and no Global Catalog server in dcdiag Want to Advertise Here? Solved Active Directory cannot connect to domain and no Global Catalog server in dcdiag Posted on 2009-09-10 https://social.technet.microsoft.com/Forums/sharepoint/en-US/4161378a-8e28-4580-a696-de4aadc1ff00/fatal-errordsgetdcname-servername-call-failed-error-1355-the-locator-could-not-find-the-server?forum=winserverDS Windows Server 2008 Active Directory DNS 1 Verified Solution 40 Comments 5,911 Views Last Modified: 2012-05-07 This is the dcdiag on PDC, GC, C:\Users...>dcdiag Directory Server Diagnosis Performing initial setup: Trying to find home server... Home Server = SMCDC01 * Identified AD Forest. Done gathering initial info. Doing initial required tests Testing server: Default-First-Site\SMCDC01 Starting test: Connectivity https://www.experts-exchange.com/questions/24720752/Active-Directory-cannot-connect-to-domain-and-no-Global-Catalog-server-in-dcdiag.html ......................... SMCDC01 passed test Connectivity Doing primary tests Testing server: Default-First-Site\SMCDC01 Starting test: Advertising Fatal Error:DsGetDcName (SMCDC01) call failed, error 1355 The Locator could not find the server. ......................... SMCDC01 failed test Advertising Starting test: FrsEvent There are warning or error events within the last 24 hours after the SYSVOL has been shared. Failing SYSVOL replication problems may cause Group Policy problems. ......................... SMCDC01 failed test FrsEvent Starting test: DFSREvent There are warning or error events within the last 24 hours after the SYSVOL has been shared. Failing SYSVOL replication problems may cause Group Policy problems. ......................... SMCDC01 failed test DFSREvent Starting test: SysVolCheck ......................... SMCDC01 passed test SysVolCheck Starting test: KccEvent ......................... SMCDC01 passed test KccEvent Starting test: KnowsOfR
onto any of his domain controllers as he was recieving the following error:The system cannot log you on due ot http://clintboessen.blogspot.com/2010/02/domain-not-found.html the following error:The specified domain either does not exist or could not be contacted.Please try again or consult your systems administrator.Also users could not get to network shares, print, or http://www.chicagotech.net/server/ad&dc1.htm even access their email via outlook. Basically their entire domain had fallen over in all locations.Running a DCDIAG on the domain provided the following output:Domain Controller DiagnosisPerforming initial setup: Done error 1355 gathering initial info.Doing initial required tests Testing server: Balcatta\ORION2 Starting test: Connectivity ......................... ORION2 passed test ConnectivityDoing primary tests Testing server: Balcatta\ORION2 Starting test: Replications [Replications Check,ORION2] A recent replication attempt failed: From ORIONCH to ORION2 Naming Context: DC=ForestDnsZones,DC=orion,DC=net,DC=au The replication generated an error (1256): Win32 Error 1256 The failure occurred at 2010-02-22 18:07:01. The last success occurred at 2010-02-22 fatal error dsgetdcname 15:22:02. 11 failures have occurred since the last success. [Replications Check,ORION2] A recent replication attempt failed: From ORIONCH to ORION2 Naming Context: DC=DomainDnsZones,DC=orion,DC=net,DC=au The replication generated an error (1256): Win32 Error 1256 The failure occurred at 2010-02-22 18:07:01. The last success occurred at 2010-02-22 15:22:02. 11 failures have occurred since the last success. [Replications Check,ORION2] A recent replication attempt failed: From ORIONCH to ORION2 Naming Context: CN=Schema,CN=Configuration,DC=orion,DC=net,DC=au The replication generated an error (-2146893022): Win32 Error -2146893022 The failure occurred at 2010-02-22 18:07:02. The last success occurred at 2010-02-22 15:22:01. 11 failures have occurred since the last success. [Replications Check,ORION2] A recent replication attempt failed: From ORIONCH to ORION2 Naming Context: CN=Configuration,DC=orion,DC=net,DC=au The replication generated an error (-2146893022): Win32 Error -2146893022 The failure occurred at 2010-02-22 18:07:02. The last success occurred at 2010-02-22 15:22:01. 11 failures have occurred since the last success. [Replications Check,ORION2] A recent replication attempt failed: From ORIONCH to ORION2 Naming Context: DC=orion,DC=net,DC=au The replication generated an error (-2146893022): Win32 Error -2146893022 The failure occurred at 2010-02-22 18:07:01. The last success occurred at 2010-02-22 15:22:01. 11