Error The Specified Domain Either Does Not Exist Or
the Community! Creating your account only takes a few minutes. Join Now Hello,I'm a little stomped on this one. It is not my AD, but one we have a trust with, the trust randomly stopped working and we
The Specified Domain Either Does Not Exist Or Could Not Be Contacted 2012
called them up and found out they are having issues with their AD.When opening ADUC or the specified domain either does not exist or could not be contacted server 2008 anything AD related they keep getting:"The Specified Domain Either Does Not Exist or Could Not Be Contacted" on both DCs.I walked them through checking
The Specified Domain Either Does Not Exist Or Could Not Be Contacted Windows 7
DNS, DNS looks good, DNS is up and running, they have static IPs and they are pointing to each other first and then to themselves.NSLookup works just fine as well. nltest /dsgetdc:$domain gets this error:nltest results: failed: Status = the specified domain either does not exist vista 1355 0x54b ERROR_NO_SUCH_DOMAIN I am a little stumped what else I can suggest them to check to get their AD back up and running.Any hints or tips appreciated. Reply Subscribe View Best Answer   15 Replies Mace OP Sosipater Jul 20, 2016 at 10:47 UTC Are they getting any replication errors? What is the output of repadmin /replsummary? 1 Mace OP Sosipater Jul 20, 2016 at 10:48 UTC Are these VMs on different the specified domain either does not exist or cannot be contacted server 2012 hosts? Have they rebooted either or both? 1 Ghost Chili OP Neally Jul 20, 2016 at 10:50 UTC Sosipater wrote:Are they getting any replication errors? What is the output of repadmin /replsummary?I don't have the actual output but he said just a bunch of errors.Sosipater wrote: Are these VMs on different hosts? Have they rebooted either or both? Yep, were both VMs on different hosts. They were not rebooted when it stopped working,but in an attempt to get them to chooch again, yeah we rebooted. 0 Mace OP Sosipater Jul 20, 2016 at 10:55 UTC Neally wrote:Sosipater wrote:Are they getting any replication errors? What is the output of repadmin /replsummary?I don't have the actual output but he said just a bunch of errors.Sosipater wrote: Are these VMs on different hosts? Have they rebooted either or both? Yep, were both VMs on different hosts. They were not rebooted when it stopped working,but in an attempt to get them to chooch again, yeah we rebooted.95% of the issues I've had with errors like that have been DNS related in some way. Without output from some of the tools, there isn't much help I can be though. 2 Ghost Chili OP Neally Jul 20, 2016 at 10:59 UTC Sosipater wrote:95% of the issues I've had with errors like that have been DNS related in some way. Without output from some
be down. Please try the request again. Your cache administrator is webmaster. Generated Fri, 14 Oct 2016 22:46:29 GMT by s_ac15 (squid/3.5.20)
WindowsWindows 10 Windows Server 2012 Windows Server 2008 Windows Server 2003 Windows 8 Windows 7 Windows Vista Windows http://windowsitpro.com/windows-server/jsi-tip-3304-specified-domain-either-does-not-exist-or-could-not-be-contacted XP Exchange ServerExchange Server 2013 Exchange Server 2010 Exchange Server 2007 Exchange Server 2003 Outlook Unified Communications/Lync SharePoint Virtualization Cloud Systems ManagementSystem Center PowerShell & Scripting Active Directory & Group Policy Mobile Networking Storage TrainingOnline Training IT/Dev Connections Webcasts VIP Library Digital Magazine Archives InfoCentersIT Innovators Mobile Computing Business Now Desktop VDI the specified All About Converged Architecture Advertisement Home > Windows > Windows Server > JSI Tip 3304. The specified domain either does not exist or could not be contacted? JSI Tip 3304. The specified domain either does not exist or could not be contacted? Jan 28, 2001 Jerold Schulman | Windows IT Pro EMAIL Tweet the specified domain Comments 2 Advertisement When you attempt to join a Windows 2000 based computer to a domain, or use Dcpromo to promote a new domain controller, you receive: The specified domain either does not exist or could not be contacted. The System Event log may contain: Event 7013 - Logon attempt with current password failed with the following error: Logon failure: unknown user name or bad password. When you run Dcdiag on the domain controller, you receive Sysvol errors. When you attempt to resolve any FSMO roles, you receive error 1355. These problems can occur if the Sysvol folder is NOT shared on the domain controller. NOTE: This behavior can occur if the DNS Server address points to your ISP's DNS server. NOTE: Do NOT use Windows Explorer to share the Sysvol. See Knowledge Base article Q257338 - Troubleshooting Missing SYSVOL and NETLOGON Shares on Windows 2000 Domain Controllers. If the Sysvol is not shared, us