[Samba] Help setting up Samba for the first time Novice user

Martin McGlensey mmcg29440 at frontier.com
Sun Sep 7 08:25:39 MDT 2014


Rowland,

Here is what I have done so far. Users marty and owner exit with the same
password on the Linux and Windows systems. The same are in the smbuseres
file with the same passwords. Both users have access permissions to the
shares in samba. I added all three ip addresses to the /etc/hosts file. Now
when I browse the network all I see is windows network. When I try to open
it (Linx) I get the following error "Unable to access location - Failure to
retrieve share list from server  - No such file or directory". If I try to
connect to a server using the "Connect to Server" option by smb://<IP>, I
get the same result.

There is a file /etc/host.allow that lists the servers that can access the
system. There is nothing in it now.

Before my changes I could at least access the Windows PC from a Linux but
now I cannot get anything.

I'll have to research the PDC or an AD DC. I don't know what they are.

Again thanks for your continued help.

Marty


-----Original Message-----
From: Rowland Penny [mailto:rowlandpenny at googlemail.com] 
Sent: Friday, September 5, 2014 3:41 PM
To: sambalist
Subject: Re: [Samba] Help setting up Samba for the first time Novice user

On 05/09/14 20:21, Martin McGlensey wrote:
> Rowland,
>
> Thanks for your reply. The fact that I am working with two Ubuntu 
> releases complicates the problem. What appears in Nautilus on the 
> 14.04 release is not in the 12.04 release. Specifically the "Connect 
> To Server" option. If I use the 14.04 version and input the IP for the 
> 12.04 PC I see the network panel (screenshot) but when I try to open 
> the remote PC the connection errors out. In the 14.04 Nautilus I see 
> Server address and a browse button , if I click on the Linux PC the 
> connection is refused.
>
> All three machines have the same user "marty" and the same password. 
> I'm the only one who uses the two Linux PC's.

> Is the user name case sensitive?

On Linux, yes!

> I do
> not know what the Samba passwords are.

How did you create the users on the Linux machines ?

> Do I have to directly assign them?

Yes.

>   On
> the Linux PC's the smbusers file shows one entry "marty=OWNER". I 
> think your saying that all three machine should have the same group of 
> users. Passwords should be the same as the login pwd. I can get to the 
> Windows PC from each Linux PC but not Linux to Linux.

Is 'marty' in /etc/passwd on the Linux machines ?

> Should I change the user name - passwords to be unique on each PC and 
> if so how?

No, the user that connects in a workgroup has to exist on EVERY machine in
the workgroup with the SAME password!!

I used to look after a workgroup that had approx 14 machines and 20 users,
it was a pain, it also used VPN connections from 3 locations and if anybody
new started, I had to connect to each location that the new user was likely
to connect to and add them to the machines there.

Could I introduce you to the possibility of using a PDC or even better an AD
DC, either would be better than a workgroup, hell, anything would be better
than a workgroup ;-)

Rowland

> Then those changes should be input into Samba?
>
> Marty
>
> -----Original Message-----
> From: Rowland Penny [mailto:rowlandpenny at googlemail.com]
> Sent: Friday, September 5, 2014 4:12 AM
> To: samba at lists.samba.org
> Subject: Re: [Samba] Help setting up Samba for the first time Novice 
> user
>
> On 04/09/14 20:19, Marty wrote:
>> Thanks for the response. Hope you will see something I missed in the 
>> conf files.
>>
>> Here are the two smb.conf files on the two Linux PC's:
>>
>> V 3.6.3
>>
>> #
>> # 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 # # Some options that are often worth 
>> tuning have been included as # commented-out examples in this file.
>> #  - When such options are commented with ";", the proposed setting
>> #    differs from the default Samba behaviour
>> #  - When commented with "#", the proposed setting is the default
>> #    behaviour of Samba but the option is considered important
>> #    enough to be mentioned here
>> #
>> # NOTE: Whenever you modify this file you should run the command # 
>> "testparm" to check that you have not made any basic syntactic # 
>> errors.
>> # A well-established practice is to name the original file # 
>> "smb.conf.master" and create the "real" config file with # testparm 
>> -s smb.conf.master >smb.conf # This minimizes the size of the really 
>> used smb.conf file # which, according to the Samba Team, impacts 
>> performance # However, use this with caution if your smb.conf file 
>> contains nested # "include" statements. See Debian bug #483187 for a 
>> case # where using a master file is not a good idea.
>> #
>>
>> #======================= 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
>>
>> # 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 host wins bcast
>>
>> #### 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 = yes
>>
>>
>>
>> #### Debugging/Accounting ####
>>
>> # This tells Samba to use a separate log file for each machine # that 
>> connects
>>      log file = /var/log/samba/log.%m
>>
>> # Cap the size of the individual log files (in KiB).
>>      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/Samba3-HOWTO/ServerType.html
>> # in the samba-doc package for details.
>> #   security = user
>>
>> # You may wish to use password encryption.  See the section on # 
>> 'encrypt passwords' in the smb.conf(5) manpage before enabling.
>> ;    encrypt passwords = yes
>>
>> # 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
>>
>> # 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 = yes
>>
>> # For Unix password sync to work on a Debian GNU/Linux system, the 
>> following # parameters must be set (thanks to Ian Kahan 
>> <<kahan at 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\s*\spassword:* %n\n
>> *Retype\snew\s*\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 = yes
>>
>> # This option controls how unsuccessful authentication attempts are 
>> mapped # to anonymous connections
>>      map to guest = bad user
>>
>> ########## 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 # (this is Samba's default)
>> #   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
>>
>> # This allows machine accounts to be created on the domain controller 
>> via the # SAMR RPC pipe.
>> # The following assumes a "machines" group exists on the system ; add 
>> machine script  = /usr/sbin/useradd -g machines -c "%u machine 
>> account" -d /var/lib/samba -s /bin/false %u
>>
>> # This allows Unix groups to be created on the domain controller via 
>> the SAMR # RPC pipe.
>> ; add group script = /usr/sbin/addgroup --force-badname %g
>>
>> ########## 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
>>
>> ############ 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/Samba3-HOWTO/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
>>
>> # 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
>>
>> # The following was the default behaviour in sarge, # but samba 
>> upstream reverted the default because it might induce # performance 
>> issues in large organizations.
>> # See Debian bug #368251 for some of the consequences of *not* # 
>> having this setting and smb.conf(5) for details.
>> ;   winbind enum groups = yes
>> ;   winbind enum users = yes
>>
>> # Setup usershare options to enable non-root users to share folders # 
>> with the net usershare command.
>>
>> # Maximum number of usershare. 0 (default) means that usershare is 
>> disabled.
>> ;    usershare max shares = 100
>>
>> # Allow users who've been granted usershare privileges to create # 
>> public shares, not just authenticated ones
>>      usershare allow guests = yes
>>      username map = /etc/samba/smbusers
>>      security = user
>> ;    guest ok = no
>> ;    guest account = nobody
>>
>> #======================= 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 director as \\server\username ;[homes]
>> ;   comment = Home Directories
>> ;   browseable = no
>>
>> # By default, the home directories are exported read-only. Change the 
>> # next parameter to 'no' if you want to be able to write to them.
>> ;   read only = yes
>>
>> # File creation mask is set to 0700 for security reasons. If you want 
>> to # create files with group=rw permissions, set next parameter to 0775.
>> ;   create mask = 0700
>>
>> # 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
>>
>> # 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 
>> # The following parameter makes sure that only "username" can connect 
>> # # This might need tweaking when using external authentication schemes
>> ;   valid users = %S
>>
>> # 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
>> ;   read only = yes
>>
>> # 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 = /var/spool/samba
>>      printable = yes
>> ;    guest ok = no
>> ;    read only = yes
>>      create mask = 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.
>> # You may need to replace 'lpadmin' with the name of the group your # 
>> admin users are members of.
>> # Please note that you also need to set appropriate Unix permissions 
>> # to the drivers directory for these users to have write rights in it
>> ;   write list = root, @lpadmin
>>
>> # A sample share for sharing your CD-ROM with others.
>> ;[cdrom]
>> ;   comment = Samba server's CD-ROM
>> ;   read only = yes
>> ;   locking = no
>> ;   path = /cdrom
>> ;   guest ok = 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
>>
>> [Share_It]
>>      comment = HP a6700y
>>      path = /home/marty/Share_It
>>      writeable = yes
>> ;    browseable = yes
>>      valid users = marty
>>
>> V 4.1.11
>>
>> #
>> # 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 # # Some options that are often worth 
>> tuning have been included as # commented-out examples in this file.
>> #  - When such options are commented with ";", the proposed setting
>> #    differs from the default Samba behaviour
>> #  - When commented with "#", the proposed setting is the default
>> #    behaviour of Samba but the option is considered important
>> #    enough to be mentioned here
>> #
>> # 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
>>
>> # This will prevent nmbd to search for NetBIOS names through DNS.
>>      dns proxy = no
>>
>> #### 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 = yes
>>
>>
>>
>> #### Debugging/Accounting ####
>>
>> # This tells Samba to use a separate log file for each machine # that 
>> connects
>>      log file = /var/log/samba/log.%m
>>
>> # Cap the size of the individual log files (in KiB).
>>      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 #######
>>
>> # Server role. Defines in which mode Samba will operate. Possible # 
>> values are "standalone server", "member server", "classic primary # 
>> domain controller", "classic backup domain controller", "active # 
>> directory domain controller".
>> #
>> # Most people will want "standalone sever" or "member server".
>> # Running as "active directory domain controller" will require first 
>> # running "samba-tool domain provision" to wipe databases and create 
>> a # new domain.
>>      server role = standalone server
>>
>> # 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
>>
>> # 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 = yes
>>
>> # For Unix password sync to work on a Debian GNU/Linux system, the 
>> following # parameters must be set (thanks to Ian Kahan 
>> <<kahan at 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\s*\spassword:* %n\n
>> *Retype\snew\s*\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 = yes
>>
>> # This option controls how unsuccessful authentication attempts are 
>> mapped # to anonymous connections
>>      map to guest = bad user
>>
>> ########## Domains ###########
>>
>> #
>> # The following settings only takes effect if 'server role = primary 
>> # classic domain controller', 'server role = backup domain controller'
>> # or '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 # (this is Samba's default)
>> #   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
>>
>> # This allows machine accounts to be created on the domain controller 
>> via the # SAMR RPC pipe.
>> # The following assumes a "machines" group exists on the system ; add 
>> machine script  = /usr/sbin/useradd -g machines -c "%u machine 
>> account" -d /var/lib/samba -s /bin/false %u
>>
>> # This allows Unix groups to be created on the domain controller via 
>> the SAMR # RPC pipe.
>> ; add group script = /usr/sbin/addgroup --force-badname %g
>>
>> ############ 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
>>
>> # 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
>>
>> # Setup usershare options to enable non-root users to share folders # 
>> with the net usershare command.
>>
>> # Maximum number of usershare. 0 (default) means that usershare is 
>> disabled.
>> ;    usershare max shares = 100
>>
>> # Allow users who've been granted usershare privileges to create # 
>> public shares, not just authenticated ones
>>      usershare allow guests = yes
>>      security = user
>> ;    encrypt passwords = yes
>> ;    guest ok = no
>> ;    guest account = nobody
>>      username map = /etc/samba/smbusers
>>
>> #======================= 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 = no
>>
>> # By default, the home directories are exported read-only. Change the 
>> # next parameter to 'no' if you want to be able to write to them.
>> ;   read only = yes
>>
>> # File creation mask is set to 0700 for security reasons. If you want 
>> to # create files with group=rw permissions, set next parameter to 0775.
>> ;   create mask = 0700
>>
>> # 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
>>
>> # 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
>> # This might need tweaking when using external authentication schemes
>> ;   valid users = %S
>>
>> # 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
>> ;   read only = yes
>>
>> # 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 = /var/spool/samba
>>      printable = yes
>> ;    guest ok = no
>> ;    read only = yes
>>      create mask = 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.
>> # You may need to replace 'lpadmin' with the name of the group your # 
>> admin users are members of.
>> # Please note that you also need to set appropriate Unix permissions 
>> # to the drivers directory for these users to have write rights in it
>> ;   write list = root, @lpadmin
>>
>> [Shared]
>>      comment = m8200n
>>      path = /home/marty/Shared
>>      writeable = yes
>>      browseable = yes
>>      valid users = marty
>>
>> I've also attached a screenshot of the network panel in the file 
>> manager - network section.
>>
>> Marty
>> On 09/04/2014 02:00 PM, samba-request at lists.samba.org wrote:
>>> Send samba mailing list submissions to
>>>      samba at lists.samba.org
>>>
>>> To subscribe or unsubscribe via the World Wide Web, visit
>>>      https://lists.samba.org/mailman/listinfo/samba
>>> or, via email, send a message with subject or body 'help' to
>>>      samba-request at lists.samba.org
>>>
>>> You can reach the person managing the list at
>>>      samba-owner at lists.samba.org
>>>
>>> When replying, please edit your Subject line so it is more specific 
>>> than "Re: Contents of samba digest..."
>>>
>>>
>>> Today's Topics:
>>>
>>>      1. Re: time sync for windows workstations (Ryan Ashley)
>>>      2. Re: time sync for windows workstations (Helmut Hullen)
>>>      3. Re: time sync for windows workstations (Helmut Hullen)
>>>      4. Re: time sync for windows workstations (Marc Muehlfeld)
>>>      5. Re: Mac OS Mavericks ?ber slow (Ryan Bair)
>>>      6. Re: AD logins fail (Yan Seiner)
>>>      7. AD logins fail (Yan Seiner)
>>>      8. Re: Mac OS Mavericks ?ber slow (Dan Mons)
>>>      9. Help setting up Samba for the first time Novice user (Marty)
>>>     10. Re: Creating users with non-ascii chars fails (Roel van Meer)
>>>     11. Re: Newer clients and security=domain (Markus Carlstedt)
>>>     12. Re: Creating users with non-ascii chars fails (solved)
>>>         (Roel van Meer)
>>>     13. Re: Newer clients and security=domain (Rowland Penny)
>>>     14. Re: Help setting up Samba for the first time Novice user
>>>         (Rowland Penny)
>>>     15. valid users fails with net groupmap rid=512 (Klaus Hartnegg)
>>>     16. Re: Newer clients and security=domain SOLVED (Markus Carlstedt)
>>>     17. samba 4 remote access to registry from windows
>>>         (Peter Grotz - Obel und Partner GbR)
>>>     18. problem with mechanism of samba user SID creation (Karel 
>>> Lang
>>> AFD)
>>>     19. samba4 + squid 2.7 auth (Agust?n Dixan D?az Corrales)
>>>     20. Re: samba4 + squid 2.7 auth (mourik jan heupink - merit)
>>>     21. Re: Mac OS Mavericks ?ber slow (Ralph B?hme)
>>>     22. Re: Mac OS Mavericks ?ber slow (Jeremy Allison)
>>>     23. samba global catalog not defined (Agust?n Dixan D?az Corrales)
>>>     24. Re: Mac OS Mavericks ?ber slow (Ralph B?hme)
>>>     25. diconnections when using roaming-profiles with samba4
>>>         (bugblatterbeast)
>>>     26. can't turn off password complexity requirements
(bugblatterbeast)
>>>     27. Re: [PATCH] Re:  S4-Winbind dumping core on password (smk_va)
>>>     28. Re: can't turn off password complexity requirements
>>>         (Rowland Penny)
>>>     29. Re: AD logins fail (Yan Seiner)
>>>     30. Re: can't turn off password complexity requirements (felix)
>>>
>>>
>>> _______________________________________________
>>> samba mailing list
>>> samba at lists.samba.org
>>> https://lists.samba.org/mailman/listinfo/samba
>>
>>
> OK, after boiling down your smb.conf's to something a bit more 
> readable, I get this global section:
>
>       workgroup = WORKGROUP
>       server string = %h server (Samba, Ubuntu)
>       dns proxy = no
>       log file = /var/log/samba/log.%m
>       max log size = 1000
>       syslog = 0
>       panic action = /usr/share/samba/panic-action %d
>       obey pam restrictions = yes
>       unix password sync = yes
>       passwd program = /usr/bin/passwd %u
>       passwd chat = *Enter\snew\s*\spassword:* %n\n
> *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
>       pam password change = yes
>       map to guest = bad user
>       usershare allow guests = yes
>       username map = /etc/samba/smbusers
>       security = user
>
> Which shows that you are running a workgroup, each machine is a 
> separate entity and users need to be created on ALL machines with the same
passwords.
>
> have you tried opening nautilus, going to 'File' -> 'Connect to Server'
> and trying to connect to the machine that way, if you cannot connect 
> via FQDN, try the machines ipaddress.
>
> I think you will find that whilst the former will not work, the later
will.
>
> Rowland
>
>
>





More information about the samba mailing list