Multiple routers in a single AD domain network

In the configutration for the lab router, set the dns server to point to the AD server. This is very likely the problem. If you do this, the router will give the Lab PCs the AD server address is the DNS server. The problem is no doubt a DNS issue.

I agree. - this was what I experienced with my test setup.

So as nerm has mentioned, it's more than likely there is no DHCP scope setup for the 192.168.2 network.

I disagree - the Domain Controller does not need to know about workstations on other DHCP scopes (unless you're using DHCP relay) - nice to have for reverse DNS, but that won't stop the workstation from logging on.
 
Thanks for the help guys. I have been busy and haven't had time to try the latest suggestions yet. I am pretty sure the issue is the scope not being set for the lab subnet, but will let you know when I try it.

Also I am trying this with a very cheap $50 Linksys router. Any chance the router just isn't sophisticated enough to work in this situation.

When I did this on my Linksys here (more sophisticated router), I disabled NAT (set to router mode, not gateway mode) , and allowed traffic all traffic from the WAN port. Have you done this?

If you don't disable NAT, your DC server will see lots of connections from the same IP address, which is not ideal.
 
When I did this on my Linksys here (more sophisticated router), I disabled NAT (set to router mode, not gateway mode) , and allowed traffic all traffic from the WAN port. Have you done this?

If you don't disable NAT, your DC server will see lots of connections from the same IP address, which is not ideal.

I was going to say the same thing, just different :p Your Linksys is technically an "Internet gateway" in that it does NAT, firewall, and routing all in one box. You need to make it only do routing, if possible.

When you do that though, the server will no longer be able to communicate with your 192.168.2.x clients because it doesn't know how to route traffic there. The Linksys in it's default mode makes traffic "look" like it is coming from an IP on the 192.168.1.x network, so the server knows where to send it's responses to. Once you shut off NAT though, it's a whole different ballgame.

You can either create an internal route in the router whose IP is specified in the servers' Local Area Connection, OR, go to the command line of the server and issue the command:

route add 192.168.2.0 mask 255.255.255.0 <ip address of Linksys router> -p

This allows the server to route traffic to the 192.168.2.x clients by sending that traffic to the IP address of the Linksys router that connects the 192.168.1.x network to the 2.x network. The "-p" makes the route persistent, so that it survives reboots.

If the route needs to be removed later, do "route delete 192.168.2.0".

Normally, I would use a more robust router such as a Mikrotik or at least a Linksys WRT-54gl that is upgraded to DD-WRT (I sell these on eBay if you are interested ;))



Eric
 
Ok here is an update guys. I resolved the dns scope issue. After doing this 3 or the workstations in the lab started working the other 27 still do not. WTF? lol I am beginning to think that luck is not on my side.

btw, Eric I can do dd-wrt myself lol :P
 
Ok here is an update guys. I resolved the dns scope issue. After doing this 3 or the workstations in the lab started working the other 27 still do not. WTF? lol I am beginning to think that luck is not on my side.

btw, Eric I can do dd-wrt myself lol :P

Can you ping the server by name and by IP from one of the workstations that does not work?

Eric
 
Can you ping the server by name and by IP from one of the workstations that does not work?

Eric

Yes, I have always been able to do that. I am wondering since it is now working on some but not all if it is a propagation issue and I just need to give it some time before trying again.
 
Why use that subnet mask?

Why not back up the subnet mask and allow the first router to handle ALL the DHCP? This isnt my baliwick but if all you need is more IP addresses on the private network...when you use 255.255.255.0 you can only have 254 hosts.
 
Back
Top