Solved

Joining Domain

Posted on 2016-07-26
9
21 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
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
 

Author Comment

by:jboyle00
ID: 41729716
Firewalls are off and IPV6 is not checked for all nics.
0
Control application downtime with dependency maps

Visualize the interdependencies between application components better with Applications Manager's automated application discovery and dependency mapping feature. Resolve performance issues faster by quickly isolating problematic components.

 
LVL 18

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 18

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 34

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

What Should I Do With This Threat Intelligence?

Are you wondering if you actually need threat intelligence? The answer is yes. We explain the basics for creating useful threat intelligence.

Join & Write a Comment

Today, still in the boom of Apple, PC's and products, nearly 50% of the computer users use Windows as graphical operating systems. If you are among those users who love windows, but are grappling to keep the system's hard drive optimized, then you s…
PRTG Network Monitor lets you monitor your bandwidth usage, so you know who is using up your bandwidth, and what they're using it for.
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.
In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're interested in additional methods for monitoring bandwidt…

757 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

Need Help in Real-Time?

Connect with top rated Experts

19 Experts available now in Live!

Get 1:1 Help Now