Windows 7 Machine can't join 2003 R2 Domain
Here's a problem I've been having with joining a W7Pro Sp1 box to a 2003 R2 Sp2 Domain:
Domain-Error-on-Join.doc
I've gone through the DNS info and cannot find where I've gone wrong. XP boxes can join the domain with no problems. I've disabled the CA RTM 8x antivirus when trying to join, but with no luck.
There are only a handful of security updates that haven't been applied to this machine, and none of them seem to have any bearing on the problem I am having.
The two errors are when I try to join the W7 machine with the domain name "EAGLE" and with the domain name "EAGLE.LOCAL". You can see a more detailed error message when I try with the .LOCAL suffix.
I followed the KB article 241515 and was able to get SRV records.
I've tried to join 3 different W7 machines and the same result.
The server reports no issues with DNS, the DHCP server is giving the correct info out regarding DNS. I verified my DNS settings on the NIC, and they are the same as other 2k3 R2 servers we have running that w7 boxes could join to--in that the dns servers actual IP was listed along with the ISP's addr.
I've restarted both DNS & DHCP....no luck w/ joining after.
I have not run any net diags or other diags...if anyone has suggestions on what's best to run, I'd like to hear them or another comments or advice. I'm not at pulling my hair out yet, but if I can't do this sometime soon, either I'll pull my hair out or it'll have already fallen off my head.
Domain-Error-on-Join.doc
I've gone through the DNS info and cannot find where I've gone wrong. XP boxes can join the domain with no problems. I've disabled the CA RTM 8x antivirus when trying to join, but with no luck.
There are only a handful of security updates that haven't been applied to this machine, and none of them seem to have any bearing on the problem I am having.
The two errors are when I try to join the W7 machine with the domain name "EAGLE" and with the domain name "EAGLE.LOCAL". You can see a more detailed error message when I try with the .LOCAL suffix.
I followed the KB article 241515 and was able to get SRV records.
I've tried to join 3 different W7 machines and the same result.
The server reports no issues with DNS, the DHCP server is giving the correct info out regarding DNS. I verified my DNS settings on the NIC, and they are the same as other 2k3 R2 servers we have running that w7 boxes could join to--in that the dns servers actual IP was listed along with the ISP's addr.
I've restarted both DNS & DHCP....no luck w/ joining after.
I have not run any net diags or other diags...if anyone has suggestions on what's best to run, I'd like to hear them or another comments or advice. I'm not at pulling my hair out yet, but if I can't do this sometime soon, either I'll pull my hair out or it'll have already fallen off my head.
did you try to set static ip address and dns on the windows7 ?
It is unclear to me whether you are setting the IP for DNS in the client. If you are, then make sure to leave out the ISP DNS servers while joining the domain.
Hope that helps....
Hope that helps....
> verified my DNS settings on the NIC, and they are the same as other 2k3 R2
> servers we have running that w7 boxes could join to--in that the dns servers
> actual IP was listed along with the ISP's addr.
This is wrong - it may not be your problem, but it definitely wrong. Your ISP doesn't give a rat's behind where your network services are, but Windows locates things through DNS lookups. If Windows decides to use the ISP servers and says "where's my global catalog", your ISP's DNS servers say "I don't know (and I don't care)"
Run IPCONFIG /ALL on BOTH your server and your problem workstation and post screen shots here.
Also, try joining the DNS domain name - meaning if your domain is mydomain and mydomain.local, try joining mydomain.local.
> servers we have running that w7 boxes could join to--in that the dns servers
> actual IP was listed along with the ISP's addr.
This is wrong - it may not be your problem, but it definitely wrong. Your ISP doesn't give a rat's behind where your network services are, but Windows locates things through DNS lookups. If Windows decides to use the ISP servers and says "where's my global catalog", your ISP's DNS servers say "I don't know (and I don't care)"
Run IPCONFIG /ALL on BOTH your server and your problem workstation and post screen shots here.
Also, try joining the DNS domain name - meaning if your domain is mydomain and mydomain.local, try joining mydomain.local.
Enter your domain DNS server (probably domain controller IP) as your client DNS - not ISP DNS.
Can you ping eagle.local?
Can you ping eagle.local?
ASKER
I may have been unclear in regards to the Server's NIC info: under the DNS info on the SERVER's NIC, I have the DNS server for the domain listed 1st (same server for DNS, DHCP, AD), then I have the ISP's info.
On the DHCP server, I have only the DNS SERVER's IP address to be handed out as DNS server.
I have tried to join both mydomain and mydomain.local, the error screenshots show the respective outcomes when I try that.
I will have to post the workstation a bit later.
Server-IPCONFIG.doc
On the DHCP server, I have only the DNS SERVER's IP address to be handed out as DNS server.
I have tried to join both mydomain and mydomain.local, the error screenshots show the respective outcomes when I try that.
I will have to post the workstation a bit later.
Server-IPCONFIG.doc
Ok, forget about DNS settings you get form DHCP for a moment. Just type your domain controller IP as your Windows 7 IPv4 Preferred DNS Server.
Then IPCONFIG /FLUSHDNS and then try to join the client to the domain.
Then IPCONFIG /FLUSHDNS and then try to join the client to the domain.
ASKER
Have already tried that. I tried it both with ipv6 enabled and disabled, but putting the DNS server info in under the ipv4 properties.
The W7 machines can see and connect to the server shares by logging on w/ domain credentials when mapping a drive.
Several months ago, we had to downgrade a w7 box to xp to get it to join this domain as the machine HAD to be on the domain. These machines are going to be on and off-site, however, we'd like to get them in AD.
I haven't taken one of these machines and tried to join them to a different domain, but I can try that if I absolutely have to.....they are not being put into production just yet, but I'd prefer if i didn't have to.
The W7 machines can see and connect to the server shares by logging on w/ domain credentials when mapping a drive.
Several months ago, we had to downgrade a w7 box to xp to get it to join this domain as the machine HAD to be on the domain. These machines are going to be on and off-site, however, we'd like to get them in AD.
I haven't taken one of these machines and tried to join them to a different domain, but I can try that if I absolutely have to.....they are not being put into production just yet, but I'd prefer if i didn't have to.
Ok. Then focus on this:
Yoyr Windows 7 client is asking his DNS server about domain controller.
And this DNS server tells your client that your 2003 R2 domain controller is called new_server_2008_eagle.loca
Looks strange to me. Check your _ldap._tcp.dc._ SRV record. unless your 2003 domain contoller is called "2008".
Yoyr Windows 7 client is asking his DNS server about domain controller.
And this DNS server tells your client that your 2003 R2 domain controller is called new_server_2008_eagle.loca
Looks strange to me. Check your _ldap._tcp.dc._ SRV record. unless your 2003 domain contoller is called "2008".
Have you tried to remove the ISP DNS info from your DNS server, flush DNS and then see if you can join?
I'm with leew, your ISP doesn't care at all.
In a nutshell, take out the ISP dns servers in your DC servers tcp entry and only have the local dns servers IP. You can add a forwarder in the dns applet and put the ISP dns servers ip in there to translate any name resolves out on the net. (provided your DC has AD, DHCP, DNS installed on the server and nothing else)
Run dcdiag /v > c:\dnstest.txt on the server.
Look at the file and see if everything passes.
Look through your DNS records and make sure they are intact, but I would think the dcdiag will tell if anythings wrong.
In a nutshell, take out the ISP dns servers in your DC servers tcp entry and only have the local dns servers IP. You can add a forwarder in the dns applet and put the ISP dns servers ip in there to translate any name resolves out on the net. (provided your DC has AD, DHCP, DNS installed on the server and nothing else)
Run dcdiag /v > c:\dnstest.txt on the server.
Look at the file and see if everything passes.
Look through your DNS records and make sure they are intact, but I would think the dcdiag will tell if anythings wrong.
ASKER
Ok, I'll follow TAWpower & kshays advice and follow those steps and post back what I find as well as the dnstest.txt file that I create.
Appreciate the feedback, we're all over worked here and need some unbiased, possibly less-worked brains to help out with this.
Appreciate the feedback, we're all over worked here and need some unbiased, possibly less-worked brains to help out with this.
I'm not overworked :)
I'm just curious why your 2003 server has name "new_server_2008" :)
I'm just curious why your 2003 server has name "new_server_2008" :)
ASKER
I found the problem(s).
Apparently this machine was renamed after it was set up as a PDC. It was changed from the "new_server_2008" to "newserver2008" as whoever named it previously didn't realize the underscores would cause issues.
After it was renamed, the DNS zones were never properly edited/updated, so what i ended up dealing with was two DNS zones that had mixed information pointing to both old and new server names, in both of them.
What I need to do, is remove the 'old' DNS zone with the underscored name, and update the actual domain local zone that everyone is in. I've gottent the name resolution to work properly, so it's just now getting rid of the bad zone and making sure the zone I'm working with is pointing to the correct locations/servers.....
Thanks for the help, it certainly made a difference in figuring out the problem.
Apparently this machine was renamed after it was set up as a PDC. It was changed from the "new_server_2008" to "newserver2008" as whoever named it previously didn't realize the underscores would cause issues.
After it was renamed, the DNS zones were never properly edited/updated, so what i ended up dealing with was two DNS zones that had mixed information pointing to both old and new server names, in both of them.
What I need to do, is remove the 'old' DNS zone with the underscored name, and update the actual domain local zone that everyone is in. I've gottent the name resolution to work properly, so it's just now getting rid of the bad zone and making sure the zone I'm working with is pointing to the correct locations/servers.....
Thanks for the help, it certainly made a difference in figuring out the problem.
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
Entered correct solution.
ASKER
Gave myself an 'attaboy'
Thanks for all the help everyone and hope this helps someone out there.
Thanks for all the help everyone and hope this helps someone out there.