Fatal Error Dsgetdcname Call Failed Error 5
Contents |
360 games PC games fatal error:dsgetdcname call failed, error 1355 server 2012 Windows games Windows phone games Entertainment All Entertainment dcgetdcname(gc_server_required) call failed error 1355 Movies & TV Music Business & Education Business Students & educators dcdiag fatal error dsgetdcname call failed error 1355 Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet restart the ntfrs service 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
Dcdiag Failed Test Locatorcheck
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
onto any of his domain controllers as he was recieving the following error:The system cannot log
Dsgetdcname Failed 0x54b
you on due ot the following error:The specified domain either does error 1355 all gc's are down not exist or could not be contacted.Please try again or consult your systems administrator.Also users could not error 1355 server 2008 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 https://support.microsoft.com/en-us/kb/958804 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 http://clintboessen.blogspot.com/2010/02/domain-not-found.html 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 C
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the http://serverfault.com/questions/34354/how-do-you-repair-active-directory-after-a-partially-renamed-domain-controller workings and policies of this site About Us Learn more about Stack https://community.spiceworks.com/topic/391566-adds-error-1355 Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered 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 error 1355 it works: Anybody can ask 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 in the domain) which crashed during a rename. As a result it left the dsgetdcname call failed 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 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 . .
Technical Consultant/SI GROUP SPONSORED BY MICROSOFT TECHNOLOGY IN THIS DISCUSSION Join the Community! Creating your account only takes a few minutes. Join Now I am in the process of migrating our ADDS to a test environment. The steps were as such: Install Win2008R2; dcpromo.exe to DC Isolate DC (separate network) Create DNS server with A records & Update rights for domain + domaincontroller Ran ipconfig /flushdns + ipconfig /registerdns Confirmed _msdcs entries in DNS server Reseize FMSO roles on DC Performed metadata cleanup Environment: Windows 2008 R2 with ADDS Roles DNS Server (separate machine) Symptoms: Best Practices Analyzer fails with 23 warnings, all related to: "This domain controller must register its correct IP addresses with the DNS server" Event ID: 1126 - Active Directory Domain Services was unable to establish a connection with the global catalog nltest /dsgetdc:domainname Getting DC name failed: Status = 1355 0x54b ERROR_NO_SUCH_DOMAIN nltest /server:lefdc /sc_query:domainname I_NetLogonControl failed: Status = 1722 0x6ba RPC_S_SERVER_UNAVAILABLE dcdiag /test:dns reports - OK dcdiag /fix - reports: Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355 A Global Catalog Server could not be located - All GC's are down. Full logs provided below: servername : LEFDC1 TextPS C:\Windows\system32> nslookup Default Server: testdns.my.domain.name Address: 10.140.1.10 > set type=all > _ldap._tcp.dc._msdcs.my.domain.name Server: testdns.my.domain.name Address: 10.140.1.10 _ldap._tcp.dc._msdcs.my.domain.name SRV service location: priority = 0 weight = 100 port = 389 svr hostname = lefdc1.my.domain.name my.domain.name nameserver = testdns.my.domain.name lefdc1.my.domain.name internet address = 10.140.1.15 testdns.my.domain.name internet address = 10.140.1.10 PS C:\Windows\system32> nltest /server:lefdc /sc_query:my.domain.name I_NetLogonControl failed: Status = 1722 0x6ba RPC_S_SERVER_UNAVAILABLE PS C:\Windows\system32> dcdiag /test:dns /v /e /f:c:\dcdiag.log PS C:\Windows\system32> nltest /dsgetdc:my.domain.name Getting DC name failed: Status = 1355 0x54b ERROR_NO_SUCH_DOMAIN PS C:\Windows\system32> ntdsutil C:\Windows\system32\ntdsutil.exe: roles fsmo maintenance: connection server connections: connect to server lefdc1.my.domain.name Binding to lefdc1.my.domain.name ... Connected to lefdc1.my.domain.name using credentials of locally logged on user. server connections: quit fsmo maintenance: seize pdc Attempting safe transfer of PDC FSMO before seizure. FSMO transferred succe