Dcdiag Fatal Error Dsgetdcname
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 dcdiag dsgetdcname error 1355 (servername) call failed, error 1355 The Locator could not find windows server 2003 error 1355 the server. Windows Server > Directory Services Question 0 Sign in to vote What acttully happen
Dcdiag Advertising Dsgetdcname
ya..? Tuesday, November 16, 2010 4:57 AM Reply | Quote Answers 0 Sign in to vote Hi It appears that your sites are not setup
Dcdiag Dsgetdcname Returned Information For
correctly 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 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 dcdiag warning dsgetdcname returned information for 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. 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
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 Time Job Ways to Get Help Expand Search
Fatal Error:dsgetdcname Call Failed, Error 1355 Server 2012
Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website fatal error:dsgetdcname call failed, error 1722 Testing Store Headlines Experts Exchange > Questions > Active Directory cannot connect to domain and no Global Catalog server in dcdiag Want dcgetdcname(gc_server_required) call failed error 1355 to Advertise Here? Solved Active Directory cannot connect to domain and no Global Catalog server in dcdiag Posted on 2009-09-10 Windows Server 2008 Active Directory DNS 1 Verified Solution 40 Comments 5,864 Views Last Modified: 2012-05-07 This 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 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 ......................... SMCDC01 passed test Connectivity Doing primary tests Testing server: Default-First-Site\SMCDC01 Starting test: Advertising https://www.experts-exchange.com/questions/24720752/Active-Directory-cannot-connect-to-domain-and-no-Global-Catalog-server-in-dcdiag.html 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: KnowsOfRoleHolders ......................... SMCDC01 passed test KnowsOfRoleHolders Starting test: MachineAccount ......................... SMCDC01 passed test MachineAccount Starting test: NCSecDesc ......................... SMCDC01 passed test NCSecDesc Starting test: NetLogons U
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 http://www.networksteve.com/forum/topic.php/A_Global_Catalog_Cannot_be_Found_on_Single_Server_A/D/?TopicId=1032&Posts=8 Sites and Services as well as having GlobalCatalogisReady = True when looking via CMD->LDP. http://clintboessen.blogspot.com/2010/02/domain-not-found.html 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 error 1355 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 dsgetdcname returned information 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. F
onto any of his domain controllers as he was recieving the following error:The system cannot log 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 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 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=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 failures h