Unable to join Win7 pro 32-bit to domain

[Cyrius]

Hi, I have been trying to join this PC to the domain, but I have been unsuccessful.

This machine is attached to some quality tracking equipment, so I called the manufacturer to see if they locked down some Windows features because this is pretty common.

Here is the error I am getting. I do not know why it would be trying to use a WINS name. The machine grabs an IP through DHCP just fine, and I can ping and remote to the AD Domain Controller, so communication is fine.

As a side not, I can access shared drives but it will not let me map them stating that it is already mapped, when it is not.

The domain name "domainname" 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 "domainname":

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

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:

4.2.2.2

x.x.x.x -this is correct

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

domainname

. (the root zone)

Edited October 25, 2011 by Cyrius

[Tripredacus]

4.2.2.2

x.x.x.x -this is correct

Do you get your DNS server info from DHCP or are you using Static info? If using Static, set your internal DNS server as the first, and the 4.2.2.2 as the secondary.

Is this network your own personal network or is it at a school/business?

[Cyrius]

It is a business network. I have not made any domain changes recently.

It is grabbing it from DHCP. I checked using ipconfig /all and x.x.x.x is showing up as the primary dns, not sure why dcdiag.txt is showing it reversed.

Also, for some reason the machine was grabbing an IP from one of the NICs on my DC from DHCP that wasn't in the DHCP scope. Also, this NIC's IP address was showing as a forward lookup zone for my DC, I removed the entry.

I disabled that NIC, I am not sure why my predecessor enabled and configured it to use this IP, but no problems have arisen from disabling it.

I think my enterprise AV may be messing with the DC, so I took it off for now. I will know where I am at after a lunch-time reboot

It turns out this problem is with my DC and not the host machine, I tested with another system that was known to be working, so I need to have this thread moved. I am running Server 2008.

Edited October 26, 2011 by Cyrius

[Cyrius]

I have dug into this and everything appears to be working correctly on the server. I think it is an AD-Integrated DNS problem, but like I said it appears to be working.

This problem is beyond me at this point.

I will be calling MS support on this one I think. I will post the solution once I have it in case anybody else comes across this.

[Cyrius]

Per the tech, the hosts weren't grabbing the correct DNS information from DHCP.

He suggested using static IPs to get the correct information, then switch over to DHCP once it is on the domain.

Seems a whole lot simpler than I had thought thanks for the help guys!

[allen2]

If you had errors when running dcdiag /test:dns on the dc and they were not fixed, then using the workaround provided ( setting the client computers with fixed ip) won't solve the problems.

[Cyrius]

I was able to join the domain after using static though.

I will try to figure out what is going on with my DNS/DHCP.

I removed a remote replication server from the DNS server list and I think that may have also helped.

Honestly right now on the DC I am jumping from issue to issue right now and I think it is all due to poor replication set up by my predecessor.

VPN through a $40 netgear at a datacenter serving 40 other customers? COME ONNNN