Bug #282

cannot join PDC domain with windows 7

Added by cpg about 12 years ago. Updated almost 12 years ago.

Target version:
Start date:
Due date:
% Done:



with win 7, attempting to join a domain does not seem to work.

even after applying the "windows xp" advice in to force the netbios name in WINS.

I had previously joined machines to this domain under Windows XP, though I cannot verify that at this moment.

Attached is a compressed tarball with the logs after running with pdc enabled and debug level 5 turned on. The file is pdc-under-w7.tar.bz2

I get a window indicating: "An Active Directory Domain Controller (AD DC) for the domain "home" could not be contacted."

Under [details>>] I get this:

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 domain name "home" might be a NetBIOS domain name.  If this is the case, verify that the domain name is properly registered with WINS.

If you are certain that the name is not a NetBIOS domain name, then the following information can help you troubleshoot your DNS configuration.

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 "home":

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.home

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:

- One or more of the following zones do not include delegation to its child zone:

. (the root zone)

pdc-under-w7.tar.bz2 - logs of the attempt to join with win7, with debug on (7.68 KB) cpg, 08/22/2009 10:40 AM


#1 Updated by cpg about 12 years ago

oh, i wonder if the mention of active directory is a giveaway.

#2 Updated by cpg about 12 years ago

after more research,

it does look like we need at least samba 3.3.4.

the latest samba for fedora 10 looks like it's 3.2.11, so we'll have to wait a bit for this.
either backport to f10 or wait to f11, which has 3.3.2 and/or perhaps samba4.

#3 Updated by andypflueger almost 12 years ago

Not dealt with Win7 that much in terms of domain membership, but I can say that Vista seems to have issues joining to a native NT4 domain. Doesn't work in my experience. I could only join Vista to a Active Directory domain even after manually adding the computer account to the domain and attempting to join. I believe they changed the TCP stack so much in Vista & Win7 and with its use of IPv6 (which I totally disable on my Vista & Win7 computers), perhaps that could be causing issues. Good luck. :)

Also available in: Atom