DFS pointing to the wrong root target (remote location instead of local)
Posted on 2008-10-25
I have two satellite offices connected with a netgear router-router VPN setup. Both locations of comcast cable with a 12/1 connection. The main office has a Dell Optiplex server running SBS2003 R2 SP2. The satellite office has a small Dell desktop with Server2003 Standard R2, SP2. I have DFS to replicate three main folders, roaming, profiles, and a shared users folder. The problem is that the clients are connecting through the VPN to the other office most of the time instead of the local share. Instead of speeding things up in the satellite office, I've now slowed things down in both! As you can imagine this is not a good situation. There is a single domain for both networks, the satellite office server with Server2003 Standard is replicating AD and DNS from the primary SBS2003 server. Login times are excessively slow, as well as simple things like accessing files, the internet, and sharepoint services. The upload bandwidth is maxed out in both locations as a result of DFS pointing the client to the wrong server! I thought this issue was resolved under Server2003 SP2? Almost sounds like a DNS issue to me but I haven't been able to peg it down. The clients are running Windows Vista Business, and there is My Documents and Desktop redirection in group policy. Offline files has also been enabled for My Documents and the Desktop. I have tried referencing either servername\roaming in the profile path in AD or the DFS root name, doesn't seem to make a difference. I know DFS + roaming profiles is not recommended, but it should be a doable setup.