Comment 50 for bug 286828
Revision history for this message
| Holger Schletz (holger-schletz) wrote | #50 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
Another workaround: set "msdfs root = no" on affected shares or in the [global] section of smb.conf. If you don't use DFS at all you can also disable it completely with "host msdfs = no".
This also made UNIX extensions finally work. Note that I had to remount all shares to get things working. I don't use DFS, so I can't tell what effect mixing DFS shares with non-DFS shares will have.
This approach has the advantage that you don't need any changes on the client side, even when the nodfs option will be available - useful if you have a lot of clients to fix.