Connecting to Domain from different subnet

Question

I am trying to connect to a domain controller that is on a different subnet..

The active directory domain controller/dns server (same box) is on the 192.168.0.0 subnet. Any computer on this same subnet can connect perfectly fine to the domain.

When I try to connect a computer that is on a different subnet, 192.168.2.0, it fails..

I get this error message when attempting to connect:

 DNS was successfully queried for the service location (SRV) resource record used to
 locate a domain controller for domain "cblad.cbl-uh.com":

 The query was for the SRV record for _ldap._tcp.dc._msdcs.dc.domain.com

All the computers DNS settings are pointing to the DNS server and NetBIOS over TCP/IP is also enabled on all the computers involved.

Any help? Thanks.

Solution

Your question is kind of all over the place and you're clearly missing some fundamentals.

255.255.0.0 and 255.255.255.0 are not subnets, they are subnet masks and are used to calculate what bits of your IP address identifies the NETWORK and what bits identify the HOST.

Example:

IP:192.168.0.1 MASK: 255.255.255.0

In this case the NETWORK(SUBNET) is 192.168.0.0, with usable addresses between 192.168.0.1 through 192.168.0.254. What this means is that a router is not required for these devices to communicate on the same physical network. If however your machine is on a different network entirely let's say 192.168.2.X then a router is required to route packets between these two networks.

So, to get to the point here, you should use the same subnet mask for all your devices, unless you're intending to segment them into seperate networks, and even then the subnet MASK will probably be the same, it's the IP addresses that will change.

Comments

[joeqwerty]

Is there a firewall between the subnets? If so, you'll invariably need to allow domain related communication through the firewall.

[SpacemanSpiff]

draw us a diagram of how things are physically connected, it will probably help out a whole lot. nothing fancy, MS paint will do.

[gravyface]

Yup, I'd start with the basics: can you ping the DC or any address on that other subnet?

[Linuz]

I updated the post.. The domain is on a 0.0 network and the workstation i want to connect is on a 2.0 network and I can ping the DC from that workstation

[SpacemanSpiff]

Then it sounds like Layer 3 is ok. You should ask yourself why the DNS query is failing, not what's wrong with the "network"

[Shyamkkhadka]

I am also facing the same issue. With above your mentioned instructions, I am getting authoritative answers with internet address as well. What might be the problem ?

[Massimo]

This has nothing to do with subnets; if this was the problem, client connectivity would everything in the network, not on a specific subnet.

[Massimo]

Also, this is a question from 2011...