If you cannot add a computer to a Windows domain (Active Directory), and it is known that there isn't a single domain controller in the subnet where the computer is located, then this note may help you.
So, we have:
a) A computer in subnet A
b) Domain controllers that are NOT located in subnet A
c) An error when adding the computer to the domain such as "the domain could not be found" or "could not connect to a domain controller".
For example, the computer is in subnet 10.0.1.0/24 and has IP 10.0.1.100, while the domain controllers are in subnet 10.0.0.0/24 and have IPs 10.0.0.1 and 10.0.0.2.
Our steps:
1) Check that the TCP/IP properties of the network adapter specify the DNS servers of our domain controllers. The primary and secondary DNS should specifically be the controllers themselves (in our example - DNS1=10.0.0.1, DNS2=10.0.0.2).
2) Check that the domain controllers are reachable and respond to DNS queries:
ping 10.0.0.1
ping 10.0.0.2
nslookup YOURDOMAIN 10.0.0.1
nslookup YOURDOMAIN 10.0.0.2
Where instead of 10.0.0.1 and 10.0.0.2 substitute the IP addresses of your domain controllers.
Instead of YOURDOMAIN enter the name of your domain.
3) In the TCP/IP properties of the network adapter, specify WINS pointing to our controllers. Even if WINS is not set up on the controllers!
For example, in our case we specify WINS with IP 10.0.0.1 and 10.0.0.2
Save, close all the settings windows, and try connecting the computer to the domain again. Having the specified WINS in place will very likely solve your problem (if the snag is there, and not in the domain controllers or something else).
Comments