GNOME Bugzilla – Bug 157922
unable to connect to share
Last modified: 2005-02-13 01:13:38 UTC
1. put smb://impinj-pc-0010 in to location bar on nautilus 2. see popup that says: "The folder contents could not be displayed. You do not have the permissions necessary to view the contents of "Windows Network: impinj-pc-0010"." I have this problem with most of the shares on my network. I am able to connect to any of these shares using smbclient, smbmount, knoqueror and xfce's file manager. To access these shares I need to provide domain name, username, and password. Nautilus is not prompting me for any of this information. I did find the gconf key for setting my samba domain and I set that correctly. Still doesn't work. This has actually never, ever worked for me and has always worked with smbclient. Thanks.
Just for some context, I can actually browse my smb network to get a listing of all the servers on my network. I just can't access them if I click on one of them.
Also strange, there are some shares where nautilus *does* correctly prompt me for password,username,domain and that works. For some shares though, it never works in nautilus. All these locations are accessible with the identical smbclient command (except the share name of course)
Which version of gnome-vfs-extras would you be using? (smb browsing is included in gnome-vfs now)
sorry for resubmitting this bug. Anyway about your question: gnome-vfs2-smb-2.8.2-8 gnome-vfs2-2.8.2-8 gnome-vfs2-devel-2.8.2-8 These are all stock from FC3 except for whatever yum updates have occurred over the last few days. There is a gnome-vfs-extras package that FC3 did not install at all. Is that for gnome 1x support? Regardless, this is exactly the behavior that I have always experience with smb in nautilus since the feature was ever available (redhat 8?). In any case, like I said, many smb shares do actually work and I do actually get prompted for username/password/domain. However there are also many shares that do not work at all. At my work we have several servers serving files via smb. Some are windows2000, some are linux with samba and some are just workstations that are sharing some local files. The only ones that actually work for me are the workstations. I did a little experiment with smbclient to find out if there were any options that were required for shares that nautilus couldn't access vs shares that nautilus could access. I discovered that for the ones that nautilus failed on, in smbclient I had to include the domain name in the smbclient command line like this: smbclient -U esalazar -W IMPINJ.COM //bugs/designs Not using the -W option caused smbclient to fail also. However, on the shares that nautilus was connecting to without problems I was able to just use the -U option like this: smbclient -U esalazar //s4200-0867975/export I know that bugs is a linux server using samba. I also needed to do that on any of our windows servers. However, s4200-0867975 is just a workstation in our lab that has some files on it that someone wanted to share out.
Not a problem with gnome-vfs-extras then.
So, what does that mean? Here is are all the gnome-vfs packages I have installed on FC3: gnome-vfs-extras-0.2.0-9 gnome-vfs2-smb-2.8.2-8 gnome-vfs2-2.8.2-8 gnome-vfs-1.0.5-21 gnome-vfs2-devel-2.8.2-8 Do those version numbers shed any light on this issue? These are the same packages (different versions for vfs2 stuff, pretty much same version numbers for vfs-* however) that Fedora had in FC2. If this is a packaging problem then it would be good to get it figured out because then we could get fedora to fix it. However, just because they have broken their packages out with different names, maybe it still is an issue with smb in gome-vfs-extras. I think that the gnome-vfs-* packages are gnome 1.x packages because when I installed those it also made me install Gconf (as opposed to GConf2) so the gnome2-vfs-smb packages is nothing more than the gnome-vfs-extras package renamed for Fedora. BTW, where is the gnome-vfs-extras tarball? I looked in the gnome ftp server with the other release packages and couldn't find it.
gnome-vfs-extras isn't even part of the 2.8.1 platform release is it? It looks like the gnome-vfs tarball has the smb stuff in it already. I'm confused by your comment "Not a problem with gnome-vfs-extras then."
*** Bug 158079 has been marked as a duplicate of this bug. ***
Looks like a bug in the smb auth code! *** This bug has been marked as a duplicate of 132933 ***