Domain does not exist or could not be contacted. Archived from groups microsoft. Now I changed password for computer account on domain controller. After restart of server SRVXX01 I see on domain controllers following security events. So I have been trying to bind my desktop Windows 10 to my virtual server Server 2016 Datacenter hosted in ESXi 6. Renegade X Black Dawn 2012 Pc Shooter here. DNS, AD, and file. A Domain Controller For The Domain Could Not Be Contacted Active Directory' title='A Domain Controller For The Domain Could Not Be Contacted Active Directory' />More infoMachines seem to have a problem browsing the directory. It most cases the error that is generated when trying to open up the Admin tools or trying to add usersgroups to our ISA Proxy server is Naming information cannot be located because The Specificed domain either does not exist or could not be contacted. Attempting to connect all of my workstations to my Domain server, I get the attached error message and, frankly, I have no clue as to what the real problem. I get the following error. An Active Directory Domain Controller for This Domain Could Not be Contacted and. I have working Internet. I have an Active Directory. When I attempt to check my trusts by right clicking on my AD Domain, I get the error you cannot modify domain or trust information because a primary. Contact your system administrator to verify that your domain is properly configured and is currently online. I press ok after chosing Admin Tools which are loaded on a worksatation and the MMC comes up with the UsersComputers snap in loaded but a red x over the directory icon. I right click on that and choose Connect to Domain then it gives you the option to put in a domain name or click the Browse button. I click the browse button and after a while about 2. Batch Rename Autocad Files on this page. THe three computers domain icon that would normally show up next to the text is missing. I select the text anyway and I get a similar error The domain domain. The specified domain either does not exist or could not be contacted. Then, if I right click on the Active Directory Users and Computers directory icon again and this time chose Connect to Domain Controller, and then I put in the nearest domain controller dc. Although browing the directory or searching the directory via My Network Places is much slower than it should be, I am able to do so. I cant, however, select Entire Directory to do a search. I must specifically select the domain underneath it we only have one domain then do a search to get results. I didnt have to do that before. This problem has become a major issue and this coming weekend were going to demote all the domain controllers except dc. Patches For M3r. DNS then repromote the DCs and reinstall DNS. This was a recommendation from a 3rd party who came in and poked around. Has anyone ever encountered an error similar to this If so, what action was taken to resolve the issuesPDC emulator cannot be contacted. Solved. Posted on 2. When I attempt to check my trusts by right clicking on my AD Domain, I get the error you cannot modify domain or trust information because a primary domain controller PDC emulator cannot be contacted. Please verify that the PDC emulator and the network are both online and functioning properly. I am not sure what is causing this. I dont know if this is the same issue or not, but I also dont know if I have a global catalog server or not, or how to make my DC a GC. Thanks for any help.