Directtechit
asked on
Domain Joining - DNS errors, Can't seem to figure it out.
We have a client that is we are converting to a domain, from a server/domain controller/workgroup PC's to one domain.
We turned setup the DNS and DHCP servers on the server, and turn that off on the Comcast box and the wireless router. Internet works, the workstations can ping the server/access shared folders, but we get the attached DNS error when trying to join each station to the domain.
IMG-2821-copy.jpg
We turned setup the DNS and DHCP servers on the server, and turn that off on the Comcast box and the wireless router. Internet works, the workstations can ping the server/access shared folders, but we get the attached DNS error when trying to join each station to the domain.
IMG-2821-copy.jpg
Cliff Galiher
Make sure your domain controllers are the ONLY dns servers your clients use. That means making sure your DHCP server is configured properly for dynamic clients and that your static clients are properly configured. If you have ISP or other DNS servers configured, lookups will fail.
To clarify, make sure the client's DNS server is your DNS server's IP. So the DNS server address for the clients (obtained by DHCP or static) should be in the LAN range; so if your Windows server is on 192.168.0.10, then your clients need to use that as the DNS server.
Additionally look at the following options within the clients TCP/IP config (Local Area Connection) for IPv4 under Advanced (see attachment). You might want to change the option I have selected and give that a try, especially if your server has a static IP.
example.PNG
Additionally look at the following options within the clients TCP/IP config (Local Area Connection) for IPv4 under Advanced (see attachment). You might want to change the option I have selected and give that a try, especially if your server has a static IP.
example.PNG
check are you able to ping DNS server with domain name..
check in DNS do you have reverse look up zone created..?
check on the work station ..
go to command prompt
type
nslookup
if it's gives proper information..
then try is there any firewall on the workstation enable if yes disable it...
or the traffice is passing through any devise.. .which is having firewall capabilities... then disable it...
all the best
check in DNS do you have reverse look up zone created..?
check on the work station ..
go to command prompt
type
nslookup
if it's gives proper information..
then try is there any firewall on the workstation enable if yes disable it...
or the traffice is passing through any devise.. .which is having firewall capabilities... then disable it...
all the best
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Yep, which is what I stated above. The DNS server IP for client workstations in a domain environment has to correspond to the Windows server's IP address that is running the DNS server service.
In addition to what's already been said, you may want to specify the full DNS domain name (e.g., eworks.local rather than simply eworks) when attempting to join it.