I have 3 sites. Site A is the main site and contain ALL servers (All windows Servers 2008). Site B and C are remote locations and contain NO servers. They are each on different subnets (Site A --> 10.1.10.X, Site B --> 10.2.10.X and Site C --> 10.3.10.X). Site B and Site C are connected to Site A by a dedicated T1 (1.5mb up and 1.5mb down). A Cisco 1841 is at each remote locations and handles DHCP. DHCP is configured to use the main domain controller at Site A for DNS. Site A uses the Domain Controller for DHCP.
Since the remote sites contain no domain controllers or even member servers, would I even need to configure anything in Active Directory Sites and Services? Wouldn't I only need to configure that if I had a Domain Controller at the remote location(s).
The issue I am trying to fix is long login times (3-5 minutes) and general slowness of the computer, especially in the mornings. This only occurs at the remote sites. The computers at the main site are very fast, as expected. Sometimes the computers at the remote locations speed up a little during the late morning/early afternoon. Other times it remains slow throughout the whole day. The computers themselves are relatively new (2-3 years old). Even just right clicking on a file on the desktop can take a couple minutes to display. Some of the programs that use a SQL database back at Site A will often freeze and crash. Normally this points to DNS, but all computers are set to use the DNS back at Site A and only that server (Not the ISP's DNS). From a remote computer, I can ping a server in Site A by name or IP address fine. We are doing folder redirection back to a server at Site A (see attached image).
Eventually I am going to put a Domain Controller at each site to at least speed up the login process, but until then I'm trying to hash out any other possible issues.
On a side note, none of the remote site computers show up in the reverse DNS zone lookup that I created for 10.2.10.X or 10.3.10.X. The do show up in the forward zone lookup though.