LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Software (https://www.linuxquestions.org/questions/linux-software-2/)
-   -   Can browse samba shares in Nautilus as root, but not as normal user (https://www.linuxquestions.org/questions/linux-software-2/can-browse-samba-shares-in-nautilus-as-root-but-not-as-normal-user-537804/)

DaneM 03-15-2007 02:14 PM

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

DaneM 03-19-2007 03:39 PM

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
#
# Example configuration of GNU Name Service Switch functionality.
# If you have the `glibc-doc' and `info' packages installed, try:
# `info libc "Name Service Switch"' for information about this file.

passwd:        compat
group:          compat
shadow:        compat

hosts:          files lmhosts wins dns winbind
networks:      files

protocols:      db files
services:      db files
ethers:        db files
rpc:            db files

netgroup:      nis

/etc/samba/smb.conf
Code:

#
# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options most of which
# are not shown in this example
#
# Any line which starts with a ; (semi-colon) or a # (hash)
# is a comment and is ignored. In this example we will use a #
# for commentary and a ; for parts of the config file that you
# may wish to enable
#
# NOTE: Whenever you modify this file you should run the command
# "testparm" to check that you have not made any basic syntactic
# errors.
#

#======================= Global Settings =======================

[global]

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of
  workgroup = WORKGROUP

# server string is the equivalent of the NT Description field
  server string = %h server (Samba, Ubuntu)

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
;  wins support = no

# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
;  wins server = w.x.y.z
;  wins server = 192.168.1.1

# This will prevent nmbd to search for NetBIOS names through DNS.
  dns proxy = no

# What naming service and in what order should we use to resolve host names
# to IP addresses
  name resolve order = lmhosts wins bcast host

#### Networking ####

# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
;  interfaces = 127.0.0.0/8 eth0

# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself.  However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
;  bind interfaces only = true



#### Debugging/Accounting ####

# This tells Samba to use a separate log file for each machine
# that connects
  log file = /var/log/samba/log.%m

# Put a capping on the size of the log files (in Kb).
  max log size = 1000

# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
;  syslog only = no

# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
  syslog = 0

# Do something sensible when Samba crashes: mail the admin a backtrace
  panic action = /usr/share/samba/panic-action %d


####### Authentication #######

# "security = user" is always a good idea. This will require a Unix account
# in this server for every user accessing the server. See
# /usr/share/doc/samba-doc/htmldocs/Samba-HOWTO-Collection/ServerType.html
# in the samba-doc package for details.
;  security = user
security = share

# You may wish to use password encryption.  See the section on
# 'encrypt passwords' in the smb.conf(5) manpage before enabling.
#  encrypt passwords = true

# If you are using encrypted passwords, Samba will need to know what
# password database type you are using. 
  passdb backend = tdbsam

#  obey pam restrictions = yes

;  guest account = nobody
  invalid users = root

# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
;  unix password sync = no

# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<kahan@informatik.tu-muenchen.de> for
# sending the correct chat script for the passwd program in Debian Sarge).
  passwd program = /usr/bin/passwd %u
  passwd chat = *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spassword:* %n\n *password\supdated\ssuccessfully* .

# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
;  pam password change = no

########## Domains ###########

# Is this machine able to authenticate users. Both PDC and BDC
# must have this setting enabled. If you are the BDC you must
# change the 'domain master' setting to no
#
;  domain logons = yes
#
# The following setting only takes effect if 'domain logons' is set
# It specifies the location of the user's profile directory
# from the client point of view)
# The following required a [profiles] share to be setup on the
# samba server (see below)
;  logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
;  logon path = \\%N\%U\profile

# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
;  logon drive = H:
;  logon home = \\%N\%U

# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
;  logon script = logon.cmd

# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe.  The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u

########## Printing ##########

# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
;  load printers = yes

# lpr(ng) printing. You may wish to override the location of the
# printcap file
;  printing = bsd
;  printcap name = /etc/printcap

# CUPS printing.  See also the cupsaddsmb(8) manpage in the
# cupsys-client package.
;  printing = cups
;  printcap name = cups

# When using [print$], root is implicitly a 'printer admin', but you can
# also give this right to other users to add drivers and set printer
# properties
;  printer admin = @lpadmin


############ Misc ############

# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
;  include = /home/samba/etc/smb.conf.%m

# Most people will find that this option gives better performance.
# See smb.conf(5) and /usr/share/doc/samba-doc/htmldocs/speed.html
# for details
# You may want to add the following on a Linux system:
#        SO_RCVBUF=8192 SO_SNDBUF=8192
  socket options = TCP_NODELAY

# The following parameter is useful only if you have the linpopup package
# installed. The samba maintainer and the linpopup maintainer are
# working to ease installation and configuration of linpopup and samba.
;  message command = /bin/sh -c '/usr/bin/linpopup "%f" "%m" %s; rm %s' &

# Domain Master specifies Samba to be the Domain Master Browser. If this
# machine will be configured as a BDC (a secondary logon server), you
# must set this to 'no'; otherwise, the default behavior is recommended.
;  domain master = auto
domain master = no
local master = no
preferred master = no
os level = 0

# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
;  idmap uid = 10000-20000
;  idmap gid = 10000-20000
;  template shell = /bin/bash

#======================= Share Definitions =======================

# Un-comment the following (and tweak the other settings below to suit)
# to enable the default home directory shares.  This will share each
# user's home directory as \\server\username
;[homes]
;  comment = Home Directories
;  browseable = yes
;  guest ok = yes
;  read only = yes
;  create mask = 0555
;  public = yes

[danehome]
  comment = Dane's home directory
  path = /home/dane
  browseable = yes
  guest ok = yes

# By default, \\server\username shares can be connected to by anyone
# with access to the samba server.  Un-comment the following parameter
# to make sure that only "username" can connect to \\server\username
;  valid users = %S

# By default, the home directories are exported read-only. Change next
# parameter to 'yes' if you want to be able to write to them.
;  writable = no

# File creation mask is set to 0600 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0664.
;  create mask = 0600

# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
;  directory mask = 0700

# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
;  comment = Network Logon Service
;  path = /home/samba/netlogon
;  guest ok = yes
;  writable = no
;  share modes = no

# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
;  comment = Users profiles
;  path = /home/samba/profiles
;  guest ok = no
;  browseable = no
;  create mask = 0600
;  directory mask = 0700

[printers]
  comment = All Printers
  browseable = no
  path = /tmp
  printable = yes
  public = no
  writable = no
  create mode = 0700

# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
  comment = Printer Drivers
  path = /var/lib/samba/printers
  browseable = yes
  read only = yes
  guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# Replace 'ntadmin' with the name of the group your admin users are
# members of.
;  write list = root, @ntadmin

# A sample share for sharing your CD-ROM with others.
;[cdrom]
;  comment = Samba server's CD-ROM
;  writable = no
;  locking = no
;  path = /cdrom
;  public = yes

# The next two parameters show how to auto-mount a CD-ROM when the
#        cdrom share is accesed. For this to work /etc/fstab must contain
#        an entry like this:
#
#      /dev/scd0  /cdrom  iso9660 defaults,noauto,ro,user  0 0
#
# The CD-ROM gets unmounted automatically after the connection to the
#
# If you don't want to use auto-mounting/unmounting make sure the CD
#        is mounted on /cdrom
#
;  preexec = /bin/mount /cdrom
;  postexec = /bin/umount /cdrom

I hope this helps somebody who has the same problem.

--Dane

oryan_dunn 12-02-2007 10:23 AM

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.

DaneM 12-02-2007 01:06 PM

I'm glad you found it helpful. I imagine that these things will get sorted out in the future (fingers crossed).

--Dane

oryan_dunn 12-03-2007 09:02 PM

Quote:

Originally Posted by DaneM (Post 2977688)
I'm glad you found it helpful. I imagine that these things will get sorted out in the future (fingers crossed).

--Dane

Well, I've done some further research.
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.

DaneM 12-04-2007 01:05 AM

Quote:

Originally Posted by oryan_dunn (Post 2979199)
I'll keep digging for an answer on Fedora 8.

Sounds good! I look forward to reading the results of your research.

--Dane

oryan_dunn 12-07-2007 04:00 PM

Quote:

Originally Posted by DaneM (Post 2979411)
Sounds good! I look forward to reading the results of your research.

--Dane

I found this thread
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.