TechnicalTim
Technical User
Well, we thought we'd venture into the world of DFS... not a great experience first time up...
We created a test DFS share as follows: \\Servername1\Shared. It was shared out as per all the normal DFS procedures - that's not my problem...
When users went to browse to \\servername2\shared or \\servername3\shared etc (existing NON-DFS shares), they were ALL directed to the DFS shared (test) folder. This was the case for any folder on the entire WAN that had the name "Shared"!! That is, I created a folder called "shared" and shared it out as "shared" and then made it a DFS folder. The issue is that the DFS settings are causing ALL the users to be misdirected the DFS folder regardless of where they are on the W2K AD domain.
So, to fix this small 'undocumented feature', I firstly stopped the DFS folder replica and basically reversed right out - including un-sharing and deleting my test folder. However, we are still (some 6 hours later) STILL having problems getting to the 'real' shared folders called 'shared' on the WAN. To workaround, I've had to re-name them all and change our login script to match and then ask everyone to log off and back on...
Anyone else encountered this undocumented 'feature'?
Any suggestions on how to permanentely fix the problem and restore the original 'shared' folder names woudl also be great.
Thanks.
We created a test DFS share as follows: \\Servername1\Shared. It was shared out as per all the normal DFS procedures - that's not my problem...
When users went to browse to \\servername2\shared or \\servername3\shared etc (existing NON-DFS shares), they were ALL directed to the DFS shared (test) folder. This was the case for any folder on the entire WAN that had the name "Shared"!! That is, I created a folder called "shared" and shared it out as "shared" and then made it a DFS folder. The issue is that the DFS settings are causing ALL the users to be misdirected the DFS folder regardless of where they are on the W2K AD domain.
So, to fix this small 'undocumented feature', I firstly stopped the DFS folder replica and basically reversed right out - including un-sharing and deleting my test folder. However, we are still (some 6 hours later) STILL having problems getting to the 'real' shared folders called 'shared' on the WAN. To workaround, I've had to re-name them all and change our login script to match and then ask everyone to log off and back on...
Anyone else encountered this undocumented 'feature'?
Any suggestions on how to permanentely fix the problem and restore the original 'shared' folder names woudl also be great.
Thanks.
