<div>
<div class="content wysiwyg-content">
I have one main network with 3DC's and another remote site with one DC (all part of the one AD). I have recently merged with another company and have a trust in place. They will be accessing resources off my network. When they logon and authenticate on my network for some reason they are being sent to the remote site DC as oppose to the main network DC's. I understand sites and services is the place to go (I think?) I have never set up this before but from my recollection I specify the IP ranges to be associated with the specific servers?
</div>
</div>


I have one main network with 3DC's and another remote site with one DC (all part of the one AD). I have recently merged with another company and have a trust in place. They will be accessing resources off my network. When they logon and authenticate on my network for some reason they are being sent to the remote site DC as oppose to the main network DC's. I understand sites and services is the place to go (I think?) I have never set up this before but from my recollection I specify the IP ranges to be associated with the specific servers?

Domain controller on seperate site

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).

Windows Server 2003

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.