if we are talking about Windows domains (when you refer to domain 1 and 2), as long as you can reach the Domain controller from 192.168.101.x network you should be fine.
For that you probably need to add a route to your router to reach from 192.168.101.x to 192.168.100.x network. Regards, Miguel ________________________________ De: James Kerr <[email protected]> Para: NT System Admin Issues <[email protected]> Enviado: Jueves 8 de marzo de 2012 14:40 Asunto: A Little Help Needed 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
