[Samba] Upgrade 3.0.24-3.fc5 to 3.0.24-4.fc5 Anomaly
kens at kensnet.org
Sun May 6 21:26:17 GMT 2007
> On Sun, 2007-05-06 at 13:51 +0100, Ken Smith wrote:
>> As part of our deployment of FC updates we have upgraded our office
>> server from 3.0.24-3 to 220.127.116.11. We got some strange results.
> This is probably related to the msdfs root default we changed in the RH
> packages (and that is going to change in 3.0.25). Have you tried to
> reboot a client and just un-map and re-map the share? That should have
> fixed it. Unfortunately this side effect can't be avoided and I
> preferred making sure we caught it sooner (less people upgraded to 24
> yet) than later.
> See also https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=235821
Thank you for your quick response and the link to bugzilla. That
clarifies the situation - I appreciate that you are also attending to
Vista issues, and it is far from a simple situation.
I just ran a test and a reboot of the Win machines does indeed fix the
problem. That wasn't a intuitive fix as it was the FC5 box that had
changed. Would it be possible to draw attention to the issue somehow
through a entry in log files or even adding "msdfs root = yes" plus some
comments into smb.conf in order to maintain compatibly with previous
behaviour. Just a suggestion.
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
More information about the samba