Typos...Typos...
Ideally you should use a different subnet at the new site and define the two subnets in Active Directory Sites and Services. You should then create two sites and assign each subnet to a site. That done you will need to chnage the IP of the DC that is going to be put on the remote site so that it is valid for its subnet. By default clients will first try to authenticate with a DC in their own site. It would also be a good idea to make sure that the second DC also has DNS installed and if a global catalog server.
To prevent unneccessary iner-site DNS traffic, if you then configure clients to use the DNS server on their own site as preferred DNS server it will reduce VPN use. If you configire clients with the IP of the DNS sever on the other subnet as the alternate DNS server this will give you a degree of resilliance should one of them failm they will automatically try use the other.
Main Topics
Browse All Topics





by: KCTSPosted on 2007-10-17 at 07:45:21ID: 20093922
Ideally you should use a different subnet at the new site and define the two subnets in Active Directory Sites and Services, You should then create two sites and assign each subnet to a site. That done you will need to chnage the IP of the DC that is going to be put on the remote site so that it is valid for the subnet. It would slao be a good idea to make sure that the second DC also has DNS installed and if a global catalog server.
If you then configure clients to use the DNS server on their own site for DNS they will then be able to use the local Domain Controller and Global Catalog for authentication thereby reducing VPN use. If you configire clients with the IP od the DNS sever on the other subnet as the alternate DNS server this will give you a degree of resilliance should one og them fail.