Comment 6 for bug 95460

I think it indeed is the same problem an in 90950: The samba share cannot be accessed from a windows machine either. (Checked from a virtual machine.)

But I'm unsure if it is really samba that were to be blamed: The smb.comf manpage (http://de.samba.org/samba/docs/man/manpages-3/smb.conf.5.html) shows no option "no/yes" for "msdfs proxy" at all. Samba would not be held responsible for interpreting a misconfigured smb.conf! (Where it might be helpful to have samba check for non-standard complying settings and to skip them by default.)

However, some yet unknown package seems to set "msdfs proxy = no" for every share when automatically upgrading from Egdy to Feisty. Thus, it might be no samba error (no misimplementation of the samba standard) but this unknown third part package causing the samba server to fail.

Why I would judge this to be rather critical is the fact that this error only becomes visible after automatic upgrade to Feisty on server systems, while the vast majority of Feisty beta testers (for obvious reasons) will have done testing on clients!