We help IT Professionals succeed at work.

Slow logon and application load times at remote office, is there a better configuration?

mcjim2k asked
Last Modified: 2010-04-21
Network Topography:
2 offices with T1's (1024Kb usable bandwidth). We are using IP Cop firewalls to create a VPN between offices. The main office has most of the servers, and all of the E-Mail is initially routed through this site. All of the servers have Windows Server 2003 installed on them, and the exchange server is using Exchange 2003 Standard SP2. The remote office has a single server with Server 2003 installed on it and is also running Exchange 2003 Standard SP2. A total of 3 AD domain controllers are configured, 2 at the main office 1 at the remote office. All of the computers are organized in OUs based on its location, but I don't know if there is any configuring that needs to happen to tell the computers to look at a specific primary one or not.

Often times users at the remote site experience slowness logging in, and files stored locally sometimes will take a very long time to open. This has been noticed on several different workstations, so i don't believe its the workstations.

Is it possible the users at the remote site are connecting to the main AD server and this is causing the slowness? What's the best way to configure the system for a setup like this.

Watch Question

This one is on us!
(Get your first solution completely free - no credit card required)


I forgot to mention. The two sites are on two different subnets. The remote workstations and the remote server are on the same sub net, but different from the main site. The remote server also acts as a DHCP and DNS server for the remote workstations.
My previous response stands.


I'll read through this, thanks a lot.


That guide was excellent, and it obviously showed me what I didn't know. I went through it and configured the sites and subnets and created the Site Links. Per the guide i configured the replication interval to be 24 hours, is this an efficient interval? Or should should i leave it at 180 minutes?

The guide mentioned a way to tell AD how much bandwidth you have between sites, but I didn't see where you would actually set that value. Where would I configure that and what value should I use for a 1024Kb pipe line?

With all of that configured, do I need to restart the domain controllers? Or will the information propagate on its own?

Site link costs are only meaningful as they are relative to each other - if you only have a single site link, the number can be set to anything.  No DC reboots required.


So if i understand this correctly, base on the computer's subnet, the computer will talk to a domain controller on the same subnet when a user logs on? So if an employee travels down to the remote site, the users computer will talk to the local domain controller.

Currently I have two Site Links in the system now, the default (DEFAULTIPSITELINK) and the new one i just made. Should i go ahead and remove the default?



Excellent resource, thank you. Things seem to be working better now.
Unlock the solution to this question.
Join our community and discover your potential

Experts Exchange is the only place where you can interact directly with leading experts in the technology field. Become a member today and access the collective knowledge of thousands of technology experts.

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.


Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.