get samba working

Raccoon1400 · 2009-04-19 21:13:06

before I installed samba, I could see other computer's shared folders on the network, but read-only.
I installed samba, but am not sure how to get it working even after reading the wiki.
What do I need to edit in the config file? Is there anything else I need to know?

pyther · 2009-04-19 22:05:02

What is it exactly that you are trying to do?

Raccoon1400 · 2009-04-19 22:11:03

I want to be able to transfer files between my computer and other computers on the network, and I want it to work both ways.

Mektub · 2009-04-20 09:21:44

Raccoon1400 wrote:

before I installed samba, I could see other computer's shared folders on the network, but read-only.
I installed samba, but am not sure how to get it working even after reading the wiki.
What do I need to edit in the config file? Is there anything else I need to know?

Most important in the config file /etc/samba/smb.conf

workgroup = YOUR WORKGROUP NAME
smb passwd file = /etc/samba/private/smbpasswd
local master = No
preferred master = No
domain master = No
os level = 30

[MyShare]
        path = /whatever/myshare
        read only = No
        force create mode = 0755

You should know what workgroup name the other computers are using.
If you want to be a local master depends on your setup. Probably not.

If you can write or not to other computers folders depends on their setup.

You should execute:

smbpasswd -a username

to set a user other computers can use to access your computer.

Start samba with '/etc/rc.conf/samba start' or put '@samba' in /etc/rc.conf'.

Mektub

Raccoon1400 · 2009-04-20 19:18:05

here's what I have so far, I made some of the changes but am not sure what do to for all of them.

# 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 (perhaps too
# many!) most of which are not shown in this example
#
# For a step to step guide on installing, configuring and using samba, 
# read the Samba-HOWTO-Collection. This may be obtained from:
#  http://www.samba.org/samba/docs/Samba-HOWTO-Collection.pdf
#
# Many working examples of smb.conf files can be found in the 
# Samba-Guide which is generated daily and can be downloaded from: 
#  http://www.samba.org/samba/docs/Samba-Guide.pdf
#
# 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 commentry 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]

# workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH
   workgroup = WORKGROUP

# server string is the equivalent of the NT Description field
   server string = Samba Server

# Security mode. Defines in which mode Samba will operate. Possible 
# values are share, user, server, domain and ads. Most people will want 
# user level security. See the Samba-HOWTO-Collection for details.
   security = user

# This option is important for security. It allows you to restrict
# connections to machines which are on your local network. The
# following example restricts access to two C class networks and
# the "loopback" interface. For more examples of the syntax see
# the smb.conf man page
;   hosts allow = 192.168.1. 192.168.2. 127.

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

# you may wish to override the location of the printcap file
;   printcap name = /etc/printcap

# on SystemV system setting printcap name to lpstat should allow
# you to automatically obtain a printer list from the SystemV spool
# system
;   printcap name = lpstat

# It should not be necessary to specify the print system type unless
# it is non-standard. Currently supported print systems include:
# bsd, cups, sysv, plp, lprng, aix, hpux, qnx
;   printing = cups

# Uncomment this if you want a guest account, you must add this to /etc/passwd
# otherwise the user "nobody" is used
;  guest account = pcguest

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

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

# Use password server option only with security = server
# The argument list may include:
#   password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name]
# or to auto-locate the domain controller/s
#   password server = *
;   password server = <NT-Server-Name>

# Use the realm option only with security = ads
# Specifies the Active Directory realm the host is part of
;   realm = MY_REALM

# Backend to store user information in. New installations should 
# use either tdbsam or ldapsam. smbpasswd is available for backwards 
# compatibility. tdbsam requires no further configuration.
;   passdb backend = tdbsam

# 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.
# Note: Consider carefully the location in the configuration file of
#       this line.  The included file is read at that point.
;   include = /usr/local/samba/lib/smb.conf.%m

# Configure Samba to use multiple interfaces
# If you have multiple network interfaces then you must list them
# here. See the man page for details.
;   interfaces = 192.168.12.2/24 192.168.13.2/24 

# Browser Control Options:
# set local master to no if you don't want Samba to become a master
# browser on your network. Otherwise the normal election rules apply
   local master = no

# OS Level determines the precedence of this server in master browser
# elections. The default value should be reasonable
   os level = 30

# Domain Master specifies Samba to be the Domain Master Browser. This
# allows Samba to collate browse lists between subnets. Don't use this
# if you already have a Windows NT domain controller doing this job
   domain master = no

# Preferred Master causes Samba to force a local browser election on startup
# and gives it a slightly higher chance of winning the election
   preferred master = no

# Enable this if you want Samba to be a domain logon server for 
# Windows95 workstations. 
;   domain logons = yes

# if you enable domain logons then you may want a per-machine or
# per user logon script
# run a specific logon batch file per workstation (machine)
;   logon script = %m.bat
# run a specific logon batch file per username
;   logon script = %U.bat

# Where to store roving profiles (only for Win95 and WinNT)
#        %L substitutes for this servers netbios name, %U is username
#        You must uncomment the [Profiles] share below
;   logon path = \\%L\Profiles\%U

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
;   wins support = yes

# 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 Proxy - Tells Samba to answer name resolution queries on
# behalf of a non WINS capable client, for this to work there must be
# at least one    WINS Server on the network. The default is NO.
;   wins proxy = yes

# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
# via DNS nslookups. The default is NO.
   dns proxy = no 

# These scripts are used on a domain controller or stand-alone 
# machine to add or delete corresponding unix accounts
;  add user script = /usr/sbin/useradd %u
;  add group script = /usr/sbin/groupadd %g
;  add machine script = /usr/sbin/adduser -n -g machines -c Machine -d /dev/null -s /bin/false %u
;  delete user script = /usr/sbin/userdel %u
;  delete user from group script = /usr/sbin/deluser %u %g
;  delete group script = /usr/sbin/groupdel %g


#============================ Share Definitions ==============================
[homes]
   comment = Home Directories
   browseable = no
   writable = yes

# Un-comment the following and create the netlogon directory for Domain Logons
; [netlogon]
;   comment = Network Logon Service
;   path = /usr/local/samba/lib/netlogon
;   guest ok = yes
;   writable = no
;   share modes = no


# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
;[Profiles]
;    path = /usr/local/samba/profiles
;    browseable = no
;    guest ok = yes


# NOTE: If you have a BSD-style print system there is no need to 
# specifically define each individual printer
[printers]
   comment = All Printers
   path = /var/spool/samba
   browseable = no
# Set public = yes to allow user 'guest account' to print
   guest ok = no
   writable = no
   printable = yes

# This one is useful for people to share files
;[tmp]
;   comment = Temporary file space
;   path = /tmp
;   read only = no
;   public = yes

# A publicly accessible directory, but read only, except for people in
# the "staff" group
;[public]
;   comment = Public Stuff
;   path = /home/samba
;   public = yes
;   writable = yes
;   printable = no
;   write list = @staff

# Other examples. 
#
# A private printer, usable only by fred. Spool data will be placed in fred's
# home directory. Note that fred must have write access to the spool directory,
# wherever it is.
;[fredsprn]
;   comment = Fred's Printer
;   valid users = fred
;   path = /homes/fred
;   printer = freds_printer
;   public = no
;   writable = no
;   printable = yes

# A private directory, usable only by fred. Note that fred requires write
# access to the directory.
;[fredsdir]
;   comment = Fred's Service
;   path = /usr/somewhere/private
;   valid users = fred
;   public = no
;   writable = yes
;   printable = no

# a service which has a different directory for each machine that connects
# this allows you to tailor configurations to incoming machines. You could
# also use the %U option to tailor it by user name.
# The %m gets replaced with the machine name that is connecting.
;[pchome]
;  comment = PC Directories
;  path = /usr/pc/%m
;  public = no
;  writable = yes

# A publicly accessible directory, read/write to all users. Note that all files
# created in the directory by users will be owned by the default user, so
# any user with access can delete any other user's files. Obviously this
# directory must be writable by the default user. Another user could of course
# be specified, in which case all files would be owned by that user instead.
;[public]
;   path = /usr/somewhere/else/public
;   public = yes
;   only guest = yes
;   writable = yes
;   printable = no

# The following two entries demonstrate how to share a directory so that two
# users can place files there that will be owned by the specific users. In this
# setup, the directory should be writable by both users and should have the
# sticky bit set on it to prevent abuse. Obviously this could be extended to
# as many users as required.
[myshare]
;   comment = Shared on duncan-arch
;   path = /home/duncan/Shared
;   valid users = duncan
;   public = no
;   writable = yes
;   printable = no
;   create mask = 0765
path = /home/duncan/Share
read only = No
force create mode = 0755

Last edited by Raccoon1400 (2009-04-20 19:25:06)

Mektub · 2009-04-20 21:32:03

Raccoon1400,

for me it looks reasonable. On the command line, with:

smbclient -L \\192.168.1.55 (substitute with an IP of a local machine)

you should see as output the shares on that machine.

Samba installs a kind of web server called 'swat' that is accessible through a browser, that lets you configure
samba will all (too many) details.

In my case 'swat' is called by 'xinetd' (which supposes that 'xinetd' is installed and running) so in /etc/xinetd.d I had
to enable 'swat':

service swat
{
        socket_type             = stream
        wait                    = no
        user                    = root
        server                  = /usr/sbin/swat
        log_on_success  += HOST DURATION
        log_on_failure  += HOST
        disable                 = no
}

After that restart 'xinetd' and access swat in your browser with:

http://localhost:901/

or

http://127.0.0.1:901/

Mektub

firecat53 · 2009-04-20 22:31:13

I can mount shares on our vista machine directly via cifs mount in the fstab, but no network browser seems to work. Here is the output of smbclient -L \\192.168.0.100 :

[firecat53@scotty ~]$ smbclient -L \\192.168.0.100
creating lame upcase table
creating lame lowcase table
Enter firecat53's password: 
Domain=[MEDIACENTER] OS=[Windows Vista (TM) Ultimate 6001 Service Pack 1] Server=[Windows Vista (TM) Ultimate 6.0]

        Sharename       Type      Comment
        ---------       ----      -------
        $VAULT$.AVG     Disk      
        ADMIN$          Disk      Remote Admin
        b_e4932         Disk      
        C               Disk      
        C$              Disk      Default share
        canon           Printer   Canon MX310 series Printer
        CBH saved Sept 9 Disk      
        controlledescent Disk      
        Data from Brent Phone Disk      
        Default         Disk      
        Default User    Disk      
        DigitalLocker   Disk      
        Documents and Settings Disk      
        drive           Disk      
        DRM             Disk      
        E               Disk      
        F               Disk      
        F$              Disk      Default share
        Feeds Cache     Disk      
        History         Disk      
        IPC$            IPC       Remote IPC
        Low             Disk      
        MapFile         Disk      
        Networking-MPSSVC-Svc Disk      
        print$          Disk      Printer Drivers
        Public          Disk      
        scottandchrystie Disk      
        Start Menu      Disk      
        Text Messages   Disk      
        Users           Disk      
        UserTile        Disk      
        Videos          Disk      
session request to 192.168.0.100 failed (Called name not present)
session request to 192 failed (Called name not present)
session request to *SMBSERVER failed (Called name not present)
NetBIOS over TCP disabled -- no workgroup available

Any ideas?

Scott

Mektub · 2009-04-20 22:54:44

firecat53,

I suppose you mean accessing remote shares through browsers like konqueror or nautilus ?

I never tried those since I avoid heavy Desk/Window Managers.

I never got pyNeighborhood to work.

"smb4k" works for me but I seldom use it. I prefer to mount shares as I need them.

Krusader, which is KDE but works well outside it, does mount shares for the simple reason that it goes through /etc/fstab.

Of course the share must be on the fstab, and this only avoids going into the command line to mount it.

Mektub

firecat53 · 2009-04-20 23:12:30

I never got nautilus to work last year when I using Ubuntu, and I can't get the Network Neighborhood function in pcmanfm-fuse to show anything, either. smbtree shows the other two machines on the network (most of the time). I can mount an ftp or ssh share just fine with pcmanfm....just can't browse the local network.

Scott

Mektub · 2009-04-20 23:18:38

You could try 'smb4k'. Works for me. Its KDE, so probably it will pull several dependencies.

Mektub

Raccoon1400 · 2009-04-20 23:46:28

I can see the stuff with smb4k, but I don't know if I can write or not because I don't see how.

When I enabled swat, neither of those commands to use it worked.

I still can't write to shared folders on other machines.

Mektub · 2009-04-21 01:22:57

smb4k must be configured (Settings --> Configure).

If you can or cannot write to shared folders depends how the remote machines have their shares configured (RW or only R).

You most probably need a password to access remote machines. On smb4k you can configure a generic user/password
combination. Individual User/Pass combinations can be assigned to a particular share by right clicking on them.

Clicking on a share should open a File Manager. Since this is a KDE application, it is opening the FM assigned on
the KDE configuration (systemsetup).

Mektub

Raccoon1400 · 2009-04-21 10:33:31

Mektub wrote:

smb4k must be configured (Settings --> Configure).
If you can or cannot write to shared folders depends how the remote machines have their shares configured (RW or only R).
You most probably need a password to access remote machines. On smb4k you can configure a generic user/password
combination. Individual User/Pass combinations can be assigned to a particular share by right clicking on them.
Clicking on a share should open a File Manager. Since this is a KDE application, it is opening the FM assigned on
the KDE configuration (systemsetup).
Mektub

On other network computers, I can write to shared folders on other machines.

Raccoon1400 · 2009-04-21 17:53:45

and what does smb4k do that I need that I can't do in nautilus?

Mektub · 2009-04-21 21:13:27

As I said in a previous post, I don't use Nautilus. Please try it and report back.

Mektub

Raccoon1400 · 2009-04-21 22:57:01

I can mount stuff in it, and when I get it to open something in a file manager, it uses nautilus, and I still can't write.

Arch Linux

#1 2009-04-19 21:13:06

get samba working

#2 2009-04-19 22:05:02

Re: get samba working

#3 2009-04-19 22:11:03

Re: get samba working

#4 2009-04-20 09:21:44

Re: get samba working

#5 2009-04-20 19:18:05

Re: get samba working

#6 2009-04-20 21:32:03

Re: get samba working

#7 2009-04-20 22:31:13

Re: get samba working

#8 2009-04-20 22:54:44

Re: get samba working

#9 2009-04-20 23:12:30

Re: get samba working

#10 2009-04-20 23:18:38

Re: get samba working

#11 2009-04-20 23:46:28

Re: get samba working

#12 2009-04-21 01:22:57

Re: get samba working

#13 2009-04-21 10:33:31

Re: get samba working

#14 2009-04-21 17:53:45

Re: get samba working

#15 2009-04-21 21:13:27

Re: get samba working

#16 2009-04-21 22:57:01

Re: get samba working

Board footer