Solved

Joining Domain

Posted on 2016-07-26
9
40 Views
Last Modified: 2016-09-09
I am having issues with joining Windows 7 clients to server 2008 r2 domain.      The machines are able to ping the PDC through name and IP address.   The clients are able to join the domain but after joining receive the following message
Changing Primary Domain DNS failed, Name will remain domain.local.

RPC server Unavailable.  

The clients that are already joined to the domain are not having any problems logging in.    
Thanks in advance for any help.
Jon
0
Comment
Question by:jboyle00
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
9 Comments
 
LVL 13

Expert Comment

by:cshepfam
ID: 41729494
Make sure those clients you are joining to the domain are not already in DNS or in AD.  Remove all instances of those computers then try again.
0
 

Author Comment

by:jboyle00
ID: 41729498
That is what we did yesterday after we started experiencing the problem.
0
 
LVL 16

Expert Comment

by:FOX
ID: 41729652
I assume all firewalls are off domain, public, and home for your DC and workstations.
Uncheck ipV6 on all your nics.


check the below as well
ref link:https://support.microsoft.com/en-us/kb/2018583
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 

Author Comment

by:jboyle00
ID: 41729716
Firewalls are off and IPV6 is not checked for all nics.
0
 
LVL 20

Expert Comment

by:Peter Hutchison
ID: 41729864
Check TCP/IPv4 settings and make sure the DNS address is pointing to your AD DNS server.
Check DNS server server is running and the Forward and ideally Reverse Lookup zones are set up and configured ok. The DC server should look at itself for DNS and forward external lookups to ISP DNS servers.
1
 

Accepted Solution

by:
jboyle00 earned 0 total points
ID: 41729874
I changed DNS IP to PDC.    This resolved the issue.  Now I have to figure out why this was the solution considering when I ran IPCONFIG /all the DNS address was the exact same address I entered.
0
 
LVL 20

Expert Comment

by:Peter Hutchison
ID: 41730738
Check the DHCP scope settings to make sure PCs pick up the correct AD DNS server address.
0
 
LVL 35

Expert Comment

by:Seth Simmons
ID: 41790973
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
0

Featured Post

Complete VMware vSphere® ESX(i) & Hyper-V Backup

Capture your entire system, including the host, with patented disk imaging integrated with VMware VADP / Microsoft VSS and RCT. RTOs is as low as 15 seconds with Acronis Active Restore™. You can enjoy unlimited P2V/V2V migrations from any source (even from a different hypervisor)

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

An article on effective troubleshooting
For anyone that has accidentally used newSID with Server 2008 R2 (like I did) and hasn't been able to get the server running again because you were unlucky (as I was) and had no backups - I was able to get things working by doing a Registry Hive rec…
Here's a very brief overview of the methods PRTG Network Monitor (https://www.paessler.com/prtg) offers for monitoring bandwidth, to help you decide which methods you´d like to investigate in more detail.  The methods are covered in more detail in o…
NetCrunch network monitor is a highly extensive platform for network monitoring and alert generation. In this video you'll see a live demo of NetCrunch with most notable features explained in a walk-through manner. You'll also get to know the philos…
Suggested Courses

624 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question