Red Hat Bugzilla – Bug 244880
Changing msdfs root default value may be an upgrade problem
Last modified: 2008-01-15 18:32:59 EST
During the 3.0.23/3.0.24 development cycle one of the default values of the
parameters controlling DFS support was changed.
msdfs root was made true by default. Later during the 3.0.25 development cycle
it was determined that this is a problem and the default has been changed back
to be false by default.
In 3.0.23c, the version we have in RHEL 5 this option is set to true. this may
be an upgrade problem from RHEL4 as well as for future versions of samba as
changing this options affects the clients connecting to the server.
This is an excerpt of the 3.0.25a release notes that explains what happens:
Changes to MS-DFS Root Share Behavior
Please be aware that the initial value for the "msdfs root" share
parameter was changed in the 3.0.25 release series and that this
option is now disabled by default. Windows clients frequently require
a reboot in order to clear any cached information about MS-DFS
root shares on a server and you may experience failures accessing
file services on Samba 3.0.25 servers until the client reboot
is performed. Alternately, you may explicitly re-enable the
parameter in smb.conf. Please refer to the smb.conf(5) man page
for more details.
Changing this option may result in issue upgrading from 5 to 5.1, but it is
advised to change it anyway as upstream has determined that defaulting to
"false" is the best thing to do.
I didn't made clear why msdfs root = yes is a problem.
Apparently Vista refuses to store roaming profiles no shares that are dfs roots.