📎 AI Summary:
The thread discusses a user experiencing difficulty logging into workstations with their server setup, despite following tutorials and having seemingly correct configurations. The primary issue appears to be DNS resolution failures, as the server cannot resolve the domain controller’s DNS name, leading to login problems. Respondents suggest verifying DHCP settings, removing the loopback address, using the router’s IP as DNS and gateway, and ensuring proper DNS configuration, with overall tone indicating troubleshooting guidance rather than frustration.

aspinall24

Member
Member details
Joined
Feb 15, 2015
Messages
2
Thread Author #1
i have covered loads of tutorials and my settings seem to be correct but i just can not get my workstations to log on.

my server has the following config 2 nic cards but one disabled due to reducing problems. nic 1 ip adress 192.168.1.200 gateway : 192.168.1.1 (my router) DNS 192.168.1.200 and 127.0.0.1 in this order.

my router is the DHCP server

Link Removed

i dont have any errors showing in the active directory section but the dns is showing the following

Link Removed

here is the settings from my IP address settings

Link Removed

as i say i have looked at various Tuts and they almost say the same my settings are correct.. IPv6 is disabled

what am i doing wrong?
 

Solution
If your DHCP is on your router at 192.168.1.1 then this server can't be reached because your dns doesn't have that number.
An image from 'windows server active directory will not allow workstations to log on'. IPv4 properties window showing manual IP, subnet, gateway, and DNS settings with a loopback IP circled.

Remove the loop-back (127.0.0.1) and put your router address instead;

P.s. your GATEWAY is the router... not the sever because the router is in control of the (gateway to the) internet!

p.p.s with older servers like this one, you are better setting the ip address to auto then reserve the number 200 at the routers dhcp settings... makes finding things on the network a bit faster.

Trouble

Noob Whisperer
Member details
Joined
Nov 30, 2009
Messages
13,723
It would help if we knew exactly what you were experiencing in the form of an error or informational dialog box when attempting to authenticate to the domain from one of your clients.
Are all your clients receiving the 192.168.1.200 address as their preferred DNS server from your router? If not you may want to fix that.
And initially at least, use the domain admin username from the client when attempting to log in just to avoid any random authentication issues.
 

aspinall24

Member
Member details
Joined
Feb 15, 2015
Messages
2
Thread Author #3
An attempt to resolve the DNS name of a domain controller in the domain being joined has failed. please confirm the client id configured to reach a DNS server that can resolve DNS names in the target domain
 

ussnorway

Windows Forum Team
Staff member
Member details
Joined
May 22, 2012
Messages
4,599
If your DHCP is on your router at 192.168.1.1 then this server can't be reached because your dns doesn't have that number.
An image from 'windows server active directory will not allow workstations to log on'. IPv4 properties window showing manual IP, subnet, gateway, and DNS settings with a loopback IP circled.

Remove the loop-back (127.0.0.1) and put your router address instead;

P.s. your GATEWAY is the router... not the sever because the router is in control of the (gateway to the) internet!

p.p.s with older servers like this one, you are better setting the ip address to auto then reserve the number 200 at the routers dhcp settings... makes finding things on the network a bit faster.
 
Last edited by a moderator:
Solution