New
#1
Can't leave (non-existent) domain, only get DNS error.
EDIT: Solved. Needed to use "Windows Enabler" -application to enable the disabled "Network ID" -button and click that.
Hi!
I used to have an Active Directory domain at home, but just recently the AD controller broke and I'm not financially capable of replacing it. So I decided to remove all computers from the domain and just use a workgroup. All the computers are personally mine, I am the sole administrator of the local computers AND the domain. There is no company and no other person to contact besides me. I have all the needed passwords and usernames (and then some) to do anything with the computers. Each computer is running Win7 x64. The AD *WAS* a 2k3 server and also acted as a intranet-DNS/internet-DNS-redirect. (And a bunch of unrelated stuff). I had a backup DNS running debian, but it went the same way (the computer was a ESXi server running several virtual machines, including the AD and the secondary DNS)
I'm a Tech Support and I've been working in places that have a domain, also I've had this domain working for at least 5 or 6 years now, so I'm not a complete noob :)
However, now I'm stuck on an error I have NEVER seen before. After I removed a few computers from the domain I started with my kids' computers... And then - hair-pulling ensued.
This is what I did:
Using account that has full local admin rights, then the "real" local "Administrator" account. It didn't matter.
Start->Computer-(rightclick)->Properties-> Change Settings (under Computer Name, domain...)
(Weirdness 1: Network ID -button is greyed out. This didn't happen with other computers. )
Clicking Change->Workgroup->name workgroup.
(Weirdness 2: although the "workgroup" radio button became selected, the greyed-out domain radio button never became UNselected.)
Display info about "you need local admin rights blah blah" -> OK
Then, I assumed I'd get that window where it asks for admin username/password, but no, what I got was an error dialog saying the "Active Directory Controller could not be reached"
Full Error Text:
Note, as said:Note: This information is intended for a network administrator. If you are not your network's administrator, notify the administrator that you received this information, which has been recorded in the file C:\Windows\debug\dcdiag.txt.
The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller (AD DC) for domain "domainname.domainext":
The error was: "DNS name does not exist."
(error code 0x0000232B RCODE_NAME_ERROR)
The query was for the SRV record for _ldap._tcp.dc._msdcs.domainname.domainext
Common causes of this error include the following:
- The DNS SRV records required to locate a AD DC for the domain are not registered in DNS. These records are registered with a DNS server automatically when a AD DC is added to a domain. They are updated by the AD DC at set intervals. This computer is configured to use DNS servers with the following IP addresses:
-- IP of my ADSL router that acts as a DHCP Server / DNS Redirect --
- One or more of the following zones do not include delegation to its child zone:
domainname.domainext
domainext
. (the root zone)
I) the ADC *does not* exist anymore
II) nor does the secondary DNS
so it is impossible to contact anything that the old domain was built on. Nothing remains.
I read a WHOLE lot of posts here and elsewhere on the web that suggested different things, including:
a) use the "real" Administrator account, not just any account with local admin rights
b) disconnect network cable and try again
c) disable all network adapters and try again
most posts just straight out said to input local admin user/pass to the window and disregarded the fact that there is NO dialog to input them. That dialog NEVER displays, I only get the ADC/DNS error dialog.
I'd really, really, REALLY hate to install everything from the start. Is there really no other option to remove the computer from the domain if that one fails?
Last edited by AnttiV; 01 Mar 2014 at 13:53. Reason: Adding info after solving the problem.