Lexluethar wrote: » Two network cards on the domain controller - devices outside of the current network are going to be clueless as to where that DC resides unless you actually connect it to that network. What specifically are you trying to accomplish? If you want to pass DHCP packets past a layer 3 router you will have to use a dhcp relay agent to accomplish that.
Lexluethar wrote: » As PJ said - smoke and mirrors... They connect to each other because they are on routable networks. While they may not be on the same subnet you can still route traffic to other subnets that aren't physically in the same location. So say you have network A and network B. Network A has your PDC and network B just has a member server. You would have to connect those two sites using some type of router (Cisco, Juniper, HP, blah blah blah) and configure the router to pass packets from one subnet to another. Once you do that a computer on Network B can say hey i'm looking for computer 192.168.1.1, that IP may not be on the same network but that router knows where to send that traffic. It's the entire point of a router and why Cisco gets paid so much money to do it.
PJ_Sneakers wrote: » It's magic. That's why Cisco guys get paid so much.
Lexluethar wrote: » I think you need a better understanding of routing in general - a lot of what you are asking for has nothing to really do with clients and servers, but more specifically routing in general and how packets are routed. I would look at some free videos on professormesser.com on the Net+ to get a better understanding of routing in general.
