Fatal Error Dsgetdcname Call Failed 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 dcdiag dsgetdcname error 1355 find the server. Windows Server > Directory Services Question 0 Sign in locator check error 1355 to vote What acttully happen ya..? Tuesday, November 16, 2010 4:57 AM Reply | Quote Answers 0 Sign in fatal error:dsgetdcname call failed, error 1355 server 2012 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 fatal error dsgetdcname call failed error 1722 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,
Dcgetdcname(gc_server_required) Call Failed Error 1355
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 follo
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
Restart The Ntfrs Service
Time Job Ways to Get Help Expand Search Submit Close Search Login Join dcdiag failed test locatorcheck Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Active dsgetdcname failed 0x54b 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: KnowsOfRol
Technical Consultant/SI GROUP SPONSORED BY MICROSOFT See more RELATED PROJECTS Computer Overhaul Replacing old desktops https://community.spiceworks.com/topic/391566-adds-error-1355 and laptops with new desktops and laptops Upgrade from XP http://www.networksteve.com/forum/topic.php/A_Global_Catalog_Cannot_be_Found_on_Single_Server_A/D/?TopicId=1032&Posts=8 to 7PRO Company I work for is having a new Customer Relationship Management Database custom built specifically for us. Needed to upgrade 50 XP PC's in Sales to Win 7. XP phase out XP is no longer being supported so all my error 1355 XP stations need to disappear before the end of the month. 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 dsgetdcname call failed 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 Ser
which has the A/D role installed and it has all 5 FSMO's in it. It shows as being set for a Global Catalog - in A/D Sites and Services as well as having GlobalCatalogisReady = True when looking via CMD->LDP. Also NLTest show GC as being installed and correct. I suspect some corruption somewhere and I have to manually change the DNS entries to point to this server. I added this to a 2003 domain, moved all FSMO roles and then removed the old DC - DSPromo failed and I had to use metadata cleanup. Now everything looks Ok in the new server except anytime I do anything with an AD account that refers to Member of I get the can't find GC error. Since the server show it is a GC and it is the same box I am not sure why it can't find itself. DNS looks correct - all mdsn records point to this server as to all _gc records. If there a way to force the system to use itself as a GC or to at least troubleshoot where the failure is?? February 6th, 2010 10:36pm Hello, are you sure you have removed all the old stale refrenceces using NTDSUTIL ??Can you please try to locate global catalogue server from the NSLOOKUP ?nslookup gc._msdcs.(YourForestDomain)and also plese post the uneditied copy of DCDIAG /V /C /D /E /s:yourdcname > c:\dcdiag.logipconfig /all and the events in the eventviewer.Thanks http://technetfaqs.wordpress.com Free Windows Admin Tool Kit Click here and download it now February 7th, 2010 9:51am Tried a couple of times to post the results but the post fails after timing out - I suspect due to size. Here is the everything but the DCDIAG results - I'll post that segmented separately. To your questions - I believe I got everything out correctly with NTDSUTIL - I included some output from queries I did today. I used the Metadata cleanup procedure from Technet so I think it was correct. The nslookup correctly returns the GC as on the server ip. The domain is isi-swens, server is Server2008-R2 and it is at IP 192.168.0.20. I do see a couple of errors in the DCDIAG output including can't find KDC but later in the output it shows this server as a KDC. FRS shows and issue in DCDIAG that it is reviewing the System Volume and can't mount SYSVOL until that is complete. The DFS is throwing an error in the event log that DFS Naming Se