<div>
If a user from domainA is logging into domainB and the only way to get the logon information is across a WAN link, the easiest way to up the speed is to place a DC from the opposite domain in the site you're logging if from. So, the site where DomainA resides will need a DC (set up as a global catalog) for DomainB and vice-versa.<br />
<br />
HTH<br />
<br />
MidnightOne
</div>


If a user from domainA is logging into domainB and the only way to get the logon information is across a WAN link, the easiest way to up the speed is to place a DC from the opposite domain in the site you're logging if from. So, the site where DomainA resides will need a DC (set up as a global catalog) for DomainB and vice-versa.

HTH

MidnightOne

<div>
hmm my guess is probably a DNS problem, i have plenty of clients logging on over the WAN with no problems at all...make sure you have conditional forwarding configured from the 2003 side of things...from the other side, point the clients to the correct DNS servers internally and see what happens, you can also apply a slow link policy with GPO
</div>


hmm my guess is probably a DNS problem, i have plenty of clients logging on over the WAN with no problems at all...make sure you have conditional forwarding configured from the 2003 side of things...from the other side, point the clients to the correct DNS servers internally and see what happens, you can also apply a slow link policy with GPO

<div>
<div class="content wysiwyg-content">
We currently have an External Trust between two domains, soon to be a Forest Trust once the other side upgrades their server to Windows 2003. &nbsp;When a laptop user from DomainA logs in from DomainB, the logon process is extremely slow over the WAN. &nbsp;<br />
<br />
What is our best solution? &nbsp;Is there a way to prevent the group policy, romaing profiles, etc.?
</div>
</div>


We currently have an External Trust between two domains, soon to be a Forest Trust once the other side upgrades their server to Windows 2003.  When a laptop user from DomainA logs in from DomainB, the logon process is extremely slow over the WAN.  

What is our best solution?  Is there a way to prevent the group policy, romaing profiles, etc.?

Cross-Forest Logon Issue

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).