We have two file servers in our DFS Namespace, a primary and a backup.
I recently changed our internal addressing scheme to allow for a larger number of hosts on the network.
The hosts who are receiving addresses from DHCP in the newly expanded range are being directed to the backup DFS server rather than the primary. The hosts with static IPs still within the old/previous range are being directed to the primary DFS server as usual.
In other words, I log in with my user account on my workstation with static IP still in the old range and I get connected to the primary DFS server. I log in with my same user account on a different workstation that has received an IP address from DHCP in the newly expanded range and I get connected to the backup DFS server.
I noticed when looking at the Namespace Servers under the DFS Management console at the backup site, that the site name for the primary site was listed as "unknown". I then remembered I needed to go into Active Directory Sites and Services, delete my old subnet what encompassed my DFS servers, and create the updated subnet to reflect the network changes I had made. After about 10 minutes or so, the "unknown" site changed back to the appropriately named primary site. But my workstations still get directed to the backup site after a reboot.
I was able, as a workstation administrator, to go under the properties of the mapped drive, click on the "DFS" tab, and set my primary site as active. The setting sticks after a reboot as well.
What I'm hoping is for someone to tell me why the workstations are not being directed to the primary site. I don't want to have to go to every individual workstation to change the mapped drive to the production drive. Thanks in advance!
Shaun