I think this is more of a network routing question. AFAIK, AD doesn't care if machines are on separate networks, as long as the DC's can communicate, and the network is correctly routed.
I'd probably standup a DC for domain 1 at site 2, to minimize traffic across the VPN. On Thu, Mar 8, 2012 at 8:40 AM, James Kerr <[email protected]> wrote: > Hello all, > > > Little road block I have hit trying to work on a project here and I need a > little advise on how to handle. > > We have two domains, I'll call them domain 1 and 2, they are in two > physical locations. Domain 1 is on subnet 192.168.100.1, domain 2 is on > 192.168.101.1. There is a VPN tunnel between the two that connects the two > domains and allows us to have a trust between the two. We want to eliminate > domain 2. We already have a domain 1 DC on the domain 2 LAN. The issue we > are having is how to get the desktops in domain 2 after the migration to > domain 1 to continue on subnet 192.168.101.1 so the VPN tunnel continues to > function how it is and so we don't run out of IP addresses. I've hit a > roadblock on how to handle this and I would love some ideas. > > James > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to [email protected] > with the body: unsubscribe ntsysadmin > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
