GNOME Bugzilla – Bug 529872
Cannot browse SMB share that requires an authentification
Last modified: 2008-11-07 13:15:11 UTC
1. Open network:/// with nautilus 2. Browse the windows network. Different networks are displayed (such as WORKGROUP) 3. Browse your workgroupe of choice. Computers of this workgroup appear 4. Browse one computer that requires authentification. What happens (gnome 2.22) : 5. The folder is empty, displaying "0 elements". Nothing else, you are stuck. What should happen (gnome 2.20) : 5. A dialog ask you for your username, domain and password. If correctly answered, the files shared on this computer are displayed. Note that using gvfs-mount to mount the remote share works perfectly and displays it on the desktop. This bug is pretty critical (IMHO) because it makes Gnome currently unusable in most corporate environment.
I think that this bug is a duplicate of Bug #524485
Peter : it looks like, indeed. I'm in an ADS environment *but* my Ubuntu doesn't use any AD integration. I just happen to be in this network.
(In reply to comment #2) > Peter : it looks like, indeed. I'm in an ADS environment *but* my Ubuntu > doesn't use any AD integration. I just happen to be in this network. > The main problem is common to both bugs: gvfs does not ask for a password during smb browsing. Therefore it is not able to show the shares on servers which require authentication for share listing. It is simple. Although there might be another issue hidden in Bug #524485 about the AD integration and Kerberos stuff. Since there is a "reported to be working" patch linked to Bug #524485 I'd recommend to open a separate bug for the AD integration issue and merge these two bugs into one. But it is only my very first personal opinion, and feel free to argue with it :-)
This could also be a duplicate of bug #522494 (and all this three issues could be the same bug).
http://www.lefred.be/?q=node/83 : is this blog post related ? It talks about a possible workaround with public=no.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 522494 ***