Can browse samba shares in Nautilus as root, but not as normal user
Hello. I've been trying for a long time to get Nautilus to browse samba shares by name, workgroup, etc. So far, I can do so if I start nautilus with "sudo nautilus --browser", but not if I do so as a regular user. When I do it as a normal user, it will show me the Windows Network, and then if I click on that, it'll show me the workgroups in the network. If I click on a workgroup, however, it will take a really long time, and eventually not show anything, popping up an error:
The folder contents could not be displayed. Sorry, couldn't display all the contents of "Windows Network: workgroup". The address that I'm trying to reach at this point is "smb://workgroup". I can see the contents of the workgroups on the network using smbtree (in the command prompt), even as a normal user, and I can ping and access all the servers by name, instead of IP address (using smbclient -L servername), also as a normal user. I think it's some sort of access/permissions problem, but I don't know for sure, and I don't really even know how to begin to solve it. I've searched the web at length. I am using Ubuntu-Dapper, fully-updated. Thanks in advance for any help you can provide! --Dane |
Solution
I've figured it out! It turns out that after I had installed winbind, started winbindd (setting it to start with the computer, using sysv-rc-conf, which I download using apt-get), and modified my smb.conf and nsswitch.conf, just restarting the samba service wasn't enough; I had to reboot too. Now I can browse properly with my non-root user. Below are my working configuration files.
/etc/nsswitch.conf Code:
# /etc/nsswitch.conf Code:
# --Dane |
As it turns out, this post was very helpful. The inability for nautilus to browse a simple windows network out of the box was very fustrating to me. I thought that maybe it was some weird settings on my windows box tripping up samba. I went so far as to install several virtual machines to create a network of "vanilla" installs of windows and linux. Even in this setup, the linux machines were unable to browse the windows network.
I just made those few changes to my CentOS 5 install, and normal users can browse the windows network just fine. Now, the question is, why don't the linux distros come preconfigured this way? It seems like such a simple small little change that could save many people many headaches. Thanks again for this tip. |
I'm glad you found it helpful. I imagine that these things will get sorted out in the future (fingers crossed).
--Dane |
Quote:
On my Fedora 8 "vanilla" install, I can't browse the network either as root or as a normal user, even after installing winbindd, samba server, and making the changes in the files. Also of interest: at work today, I fired up my Fedora 5 install, and it's settings were setup as default out of the box. Even as a normal user in this environment, browsing a windows network works just fine. I have no idea how the backends are setup here, but I do know that it is a domain network, not a workgroup network. I'll keep digging for an answer on Fedora 8. |
Quote:
--Dane |
Quote:
http://forums.fedoraforum.org/forum/...ead.php?t=1892 I know its older, but I'm going to give it a try. Look at posts 5 and 11. It looks like it may only browse when a samba machine is the domain master. I'll post my results when I get home tonight. EDIT: but then what happens if you want to have multiple fedora 8 boxes, that could join or leave a network? if two samba servers are set to master, do they both try to be master, or do they work out one being the master and the other a slave? |
All times are GMT -5. The time now is 02:27 PM. |