Dsgetdcname Error
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 find the server. Windows Server > Directory Services fatal error:dsgetdcname call failed, error 1355 server 2012 Question 0 Sign in to vote What acttully happen ya..? Tuesday, November 16, 2010 dcgetdcname(gc_server_required) call failed error 1355 4:57 AM Reply | Quote Answers 0 Sign in to vote Hi It appears that your sites are not setup correctly dcdiag fatal error dsgetdcname call failed error 1355 or you have added new IP subnets that are not specified in current Sites. You will need to identify the client PCs in your netlogon.log and make sure that you have defined them in all gc are down error 1355 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, 2010 9:28 AM Reply | Quote 0 Sign in to vote Hello, 2. the other ipconfig /all are missing, especially from the problem machines.
Restart The Ntfrs Service
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 following files for research. Please collect the following files on BKRBR0223DC110: dcdiag /v >c:\dcdiag.txt netdiag /v >c:\netdiag.txt ipconfig /all > c:\ipconfig.txt Please also run the following command on one problematic XP client: ipconfig /all > c:\ipconfig.txt Upload these file to the following workspace. ----------------------------------
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 more about hiring developers or posting
Error 1355 Server 2008
ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a dcdiag error 1355 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 dsgetdcname failed 0x54b a question Anybody can answer The best answers are voted up and rise to the top How do you repair active directory after a partially renamed domain controller? up vote 2 down vote favorite I have a 2008 Server (only DC 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 in the domain) which crashed during a rename. As a result it left the system half renamed. The computer name had been changed to DC1 but there were still many references to DC2 (the old computer name) such as in DNS and Active directory. As a result the Netlogon service will not start and Active directory cannot be accessed. After about 8 hours of hard work, I manged to make some progress by manualy editing DNS records and update Active Directory records using http://serverfault.com/questions/34354/how-do-you-repair-active-directory-after-a-partially-renamed-domain-controller ADSIEdit. When i run netdiag i get the following output... Computer Name: DC1 DNS Host Name: dc1.school.local System info : Windows Server (R) 2008 Standard (Build 6002) Processor : x86 Family 6 Model 15 Stepping 11, GenuineIntel Hotfixes : none detected Netcard queries test . . . . . . . : Passed [WARNING] The net card 'RAS Async Adapter' may not be working because it has not received any packets. GetStats failed for 'isatap.{A9F5A39A-FD61-44C4-BE9F-1E4BD5A3B546}'. [ERROR_GEN_FAILURE] Per interface results: Adapter : Local Area Connection Netcard queries test . . . : Passed Host Name. . . . . . . . . : dc1 IP Address . . . . . . . . : 192.168.1.3 Subnet Mask. . . . . . . . : 255.255.255.0 Default Gateway. . . . . . : 192.168.1.1 Dns Servers. . . . . . . . : 192.168.1.3 127.0.0.1 AutoConfiguration results. . . . . . : Passed Default gateway test . . . : Passed NetBT name test. . . . . . : Passed [WARNING] At least one of the <00> 'WorkStation Service', <03> 'Messenger Service', <20> 'WINS' names is missing. WINS service test. . . . . : Skipped There are no WINS servers configured for this interface. Global results: Domain membership test . . . . . . : Passed NetBT transports test. . . . . . . : Passed List of NetBt transports currently configured: NetBT_Tcpip_{A9F5A39A-FD61-44C4-BE9F-1E4BD5A3B546} 1 NetBt transport currently configured. Autonet addr
onto any of his domain controllers as he was recieving the following error:The system cannot log http://clintboessen.blogspot.com/2010/02/domain-not-found.html you on due ot 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 even access their email via outlook. Basically their entire domain had fallen over in all locations.Running a DCDIAG on the domain provided error 1355 the following output:Domain Controller DiagnosisPerforming initial setup: Done 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 error 1355 server 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: 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=orio