Comment 45 for bug 209520

@Sebastien Bacher

I think I found the reason why gvfs on Hardy failed to connect to a Samba or Windows share:

1/ On the server side, if the security mode in sbm.conf is set to "user" then Hardy client can connect using gvfs just fine.
2/ If on the server side, the security mode is "share" then Hardy client that use gvfs will have problem.
3/ On the Gusty client, it can make the connection as smb://server/share in either cases.

I tested by changing the single line in the sbm.conf file, in the [global] section:

security = user

into

security = share

then all Hardy client can not authenticate any more.

So, for now, if anyone run your own Samba server then the work around would be to use "security = users".

Hope this helps and looking forward to the fix.

Cheers,