Page 3 of 4 FirstFirst 1234 LastLast
Results 21 to 30 of 40

Thread: Samba on Ubuntu 13.10

  1. #21
    Join Date
    May 2008
    Location
    SoCal
    Beans
    Hidden!
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: Samba on Ubuntu 13.10

    Quote Originally Posted by ray_silva View Post
    I guess I really messed it up. Yes, there appear to be old multiple copies of the samba config file.

    Code:
    ray@ray-desktop:~$ ls -l /etc/samba
    total 32
    -rw-r--r-- 1 root root     8 Nov 23  2012 gdbcommands
    -rw-r--r-- 1 root root  3533 Mar 30 16:36 smb2.conf
    -rw-r--r-- 1 ray  ray    694 Mar 30 17:06 smb.conf
    -rw-r--r-- 1 root root 12599 Mar 30 15:47 smb.conf.old.gadmin-samba-0.3.2
    -rw-r--r-- 1 root root    91 Mar 30 15:47 smbusers
    -rw-r--r-- 1 root root     0 Mar 30 15:24 user.map
    All of those appear to be modified in some manner. Post the complete output of this
    Code:
    cat /etc/samba/smb.conf.old.gadmin-samba-0.3.2
    This may be the original. I will look at it and see if we can use it.
    -BAB1

  2. #22
    Join Date
    Jan 2011
    Location
    SoFla
    Beans
    44
    Distro
    Ubuntu 14.04 Trusty Tahr

    Re: Samba on Ubuntu 13.10

    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
    #
    # 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]
    	log file = /var/log/samba/log.%m
    	passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
    	obey pam restrictions = yes
    	username map = /etc/samba/user.map
    	map to guest = bad user
    	encrypt passwords = yes
    	passwd program = /usr/bin/passwd %u
    	dns proxy = no
    	server string = %h server (Samba, Ubuntu)
    	path = /home
    	default = home
    	unix password sync = yes
    	remote announce = 192.168.0.194
    	workgroup = WORKGROUP
    	os level = 20
    	syslog = 0
    	panic action = /usr/share/samba/panic-action %d
    	usershare allow guests = yes
    	max log size = 1000
    	pam password change = yes
    
    
    ## Browsing/Identification ###
    
    
    # Change this to the workgroup/NT-domain name your Samba server will part of
    
    
    # server string is the equivalent of the NT Description field
    
    
    # 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.
    
    
    # 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 wlan0
    # 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
    
    
    # Cap the size of the individual log files (in KiB).
    
    
    # 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.
    
    
    # Do something sensible when Samba crashes: mail the admin a backtrace
    
    
    
    
    ####### 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.
    
    
    # If you are using encrypted passwords, Samba will need to know what
    # password database type you are using.  
    ;	passdb backend = tdbsam
    
    
    
    
    # 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.
    
    
    # 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).
    
    
    # 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'.
    
    
    # This option controls how unsuccessful authentication attempts are mapped
    # to anonymous connections
    
    
    ########## 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
    
    
    #======================= 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
    
    
    [home]
    	path = /home
    	writeable = yes
    ;	browseable = yes
    	valid users = ray
    I gotta admit I found this file totally confusing. I don't see anywhere in it where one would put the individual Windows machines on the network that would share - not iP addresses, not usernames, not passwords - nothing. That's why I tried Webmin. It was hardly any less confusing. I've been reading the Webmin manual to try to understand, but some entries that should be simple are nowhere simply explained.

    Maybe you can figure if something in this is at least usable.

    I have also been reading that it is harder to get Windows 7 machines to share because of something Windows did after XP (which was apparently an easy share).

    I also saw that the firewall may be blocking (but it didn't before when I was at least able to see the Windows network & access files - I can't now). Anyway, I have turned it off just in case.

    All this is because I wanted to set up my Ubuntu machine to operate as a file server to the Windows Networked machines where all files could be stored and retrieved from.

    Again, Thanks.

  3. #23
    Join Date
    May 2008
    Location
    SoCal
    Beans
    Hidden!
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: Samba on Ubuntu 13.10

    Quote Originally Posted by ray_silva View Post
    I gotta admit I found this file totally confusing. I don't see anywhere in it where one would put the individual Windows machines on the network that would share - not iP addresses, not usernames, not passwords - nothing. That's why I tried Webmin. It was hardly any less confusing. I've been reading the Webmin manual to try to understand, but some entries that should be simple are nowhere simply explained.
    You have a completely erroneous idea of what the smb.conf file is for. It's not to add Windows machines, IP addresses or passwords at all. It's purpose is to configure the smbd and nmbd daemons (processes) so that the Samba server can serve files to clients that request them. The only database exists outside of the smb.conf file. The computer name recognition is all handled internally by the two processes via NETBIOS discovery.
    Maybe you can figure if something in this is at least usable.
    It's going to be easier to provide you a known (to me) good smb.conf file and have you copy it over.
    I have also been reading that it is harder to get Windows 7 machines to share because of something Windows did after XP (which was apparently an easy share).
    The change was to using SMB2 instead of just SMB (CIFS). This has now also includes SMB3. The bottom line is that Samba has been updated and the original configuration file is still the same.
    I also saw that the firewall may be blocking (but it didn't before when I was at least able to see the Windows network & access files - I can't now). Anyway, I have turned it off just in case.
    I'd rather diagnose what you have rather than guess at the problem.
    All this is because I wanted to set up my Ubuntu machine to operate as a file server to the Windows Networked machines where all files could be stored and retrieved from.
    This is doable. I have Samba servers running as we speak.

    If you want to keep the file you are presently using you will need to rename it.
    Code:
    sudo mv /etc/samba/smb.conf /etc/samba/smb.conf.notworking
    I am attaching a default smb.conf file (with the name smb.conf.txt). Copy that file to your home directory. Then copy this file you downloaded from me to the /etc/samba directory. Then change the ownership to root:root with this command
    Code:
    sudo chown root:root /etc/samba/smb.conf.txt
    ...Now you need to rename it using this command
    Code:
    sudo mv /etc/samba/smb.conf.txt /etc/samba/smb.conf
    Then reload Samba with this
    Code:
    sudo service smbd restart
    Then post the output of this again
    Code:
    sudo pdbedit -L
    After we get this running if you have questions I will either answer or direct you to the appropriate site. For now just follow along.
    Attached Files Attached Files
    -BAB1

  4. #24
    Join Date
    Jan 2011
    Location
    SoFla
    Beans
    44
    Distro
    Ubuntu 14.04 Trusty Tahr

    Re: Samba on Ubuntu 13.10

    OK, after doing that, upon reloading Samba with the sudo service smbd restart command from Terminal, my browser crashed. When I reopened it and ran the sudo pdbedit -L command. I got this.

    Code:
    ray:1000:ray
    smbguest:1001:Samba guest account
    root:0:root
    But Ubuntu machine cannot now even see the Windows network computers as it was able to do before.

    I restarted the Windows network computers. They all see each other fine, but do not see the Ubuntu computer at all.

    I'm studying the new config file to see exactly what is different in it.

    Now that you mention NETBIOS, I checked my router's DHCP settings. I have no WINS server configured. Is that necessary? I didn't think so because the router is having no problem assigning an IP address to the Ubuntu computer on the network. The DHCP server is always broadcasting.

  5. #25
    Join Date
    Jan 2011
    Location
    SoFla
    Beans
    44
    Distro
    Ubuntu 14.04 Trusty Tahr

    Re: Samba on Ubuntu 13.10

    After a little time now the Ubuntu machine running samba CAN see the Windows WORKGROUP on the Windows network.

    So we are back to at least Ubuntu seeing and accessing the filed on the Windows network.

    Now - what I need is for any of the Windows computers to see the Ubuntu machine and access its shared files.

  6. #26
    Join Date
    May 2008
    Location
    SoCal
    Beans
    Hidden!
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: Samba on Ubuntu 13.10

    Quote Originally Posted by ray_silva View Post
    After a little time now the Ubuntu machine running samba CAN see the Windows WORKGROUP on the Windows network.

    So we are back to at least Ubuntu seeing and accessing the filed on the Windows network.

    Now - what I need is for any of the Windows computers to see the Ubuntu machine and access its shared files.
    I want you to make a copy of the smb.conf file with this command
    Code:
    sudo cp /etc/samba/smb.conf /etc/samba/original
    Then I want you to edit your smb.conf file. We need to add this line just under the [global] label. It should look like this
    Code:
    netbios name = ray_server
    ...Edit: you need to restart the samba daemon for this to take effect. To do that you need to use this command
    Code:
    sudo service smbd restart
    This will cause the server to broadcast it's name on the local network.

    DO NOT change anything else. We have made progress the samba data base is working correctly now, To see this you can use this
    Code:
    smbtree -d3
    ...post the output fro me to see too.
    Last edited by bab1; April 6th, 2014 at 04:54 PM.
    -BAB1

  7. #27
    Join Date
    Jan 2011
    Location
    SoFla
    Beans
    44
    Distro
    Ubuntu 14.04 Trusty Tahr

    Re: Samba on Ubuntu 13.10

    smbtree -d3 results (after restarting smbd service)


    Code:
    lp_load_ex: refreshing parameters
    Initialising global parameters
    rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
    params.c:pm_process() - Processing configuration file "/etc/samba/smb.conf"
    Processing section "[global]"
    added interface ham0 ip=2620:9b::190c:bd2e bcast=2620:9b::ffff:ffff netmask=ffff:ffff:ffff:ffff:ffff:ffff::
    added interface wlan0 ip=fe80::208:54ff:fe8d:99f%wlan0 bcast=fe80::ffff:ffff:ffff:ffff%wlan0 netmask=ffff:ffff:ffff:ffff::
    added interface ham0 ip=fe80::7879:19ff:fe0c:bd2e%ham0 bcast=fe80::ffff:ffff:ffff:ffff%ham0 netmask=ffff:ffff:ffff:ffff::
    added interface wlan0 ip=192.168.0.194 bcast=192.168.0.255 netmask=255.255.255.0
    added interface ham0 ip=25.12.189.46 bcast=25.255.255.255 netmask=255.0.0.0
    Enter ray's password: 
    tdb(/var/run/samba/gencache.tdb): tdb_open_ex: could not open file /var/run/samba/gencache.tdb: Permission denied
    resolve_lmhosts: Attempting lmhosts lookup for name WORKGROUP<0x1d>
    resolve_lmhosts: Attempting lmhosts lookup for name WORKGROUP<0x1d>
    name_resolve_bcast: Attempting broadcast lookup for name WORKGROUP<0x1d>
    resolve_lmhosts: Attempting lmhosts lookup for name WORKGROUP<0x1b>
    resolve_lmhosts: Attempting lmhosts lookup for name WORKGROUP<0x1b>
    resolve_wins: Attempting wins lookup for name WORKGROUP<0x1b>
    resolve_wins: WINS server resolution selected and no WINS servers listed.
    name_resolve_bcast: Attempting broadcast lookup for name WORKGROUP<0x1b>
    name_resolve_bcast: Attempting broadcast lookup for name __MSBROWSE__<0x1>
    I figure the ham0 interfaces are from hamachi for my mobile phone connectivity. I have no idea why genache.tdb is denying permission. Should I have run the smbtree command in sudo? Just in case so, here's the result running it in sudo

    Code:
    lp_load_ex: refreshing parameters
    Initialising global parameters
    rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
    params.c:pm_process() - Processing configuration file "/etc/samba/smb.conf"
    Processing section "[global]"
    added interface ham0 ip=2620:9b::190c:bd2e bcast=2620:9b::ffff:ffff netmask=ffff:ffff:ffff:ffff:ffff:ffff::
    added interface wlan0 ip=fe80::208:54ff:fe8d:99f%wlan0 bcast=fe80::ffff:ffff:ffff:ffff%wlan0 netmask=ffff:ffff:ffff:ffff::
    added interface ham0 ip=fe80::7879:19ff:fe0c:bd2e%ham0 bcast=fe80::ffff:ffff:ffff:ffff%ham0 netmask=ffff:ffff:ffff:ffff::
    added interface wlan0 ip=192.168.0.194 bcast=192.168.0.255 netmask=255.255.255.0
    added interface ham0 ip=25.12.189.46 bcast=25.255.255.255 netmask=255.0.0.0
    Enter root's password: 
    resolve_lmhosts: Attempting lmhosts lookup for name WORKGROUP<0x1d>
    resolve_lmhosts: Attempting lmhosts lookup for name WORKGROUP<0x1d>
    name_resolve_bcast: Attempting broadcast lookup for name WORKGROUP<0x1d>
    resolve_lmhosts: Attempting lmhosts lookup for name WORKGROUP<0x1b>
    resolve_lmhosts: Attempting lmhosts lookup for name WORKGROUP<0x1b>
    resolve_wins: Attempting wins lookup for name WORKGROUP<0x1b>
    resolve_wins: WINS server resolution selected and no WINS servers listed.
    name_resolve_bcast: Attempting broadcast lookup for name WORKGROUP<0x1b>
    name_resolve_bcast: Attempting broadcast lookup for name __MSBROWSE__<0x1>

  8. #28
    Join Date
    May 2008
    Location
    SoCal
    Beans
    Hidden!
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: Samba on Ubuntu 13.10

    Quote Originally Posted by ray_silva View Post
    I figure the ham0 interfaces are from hamachi for my mobile phone connectivity. I have no idea why genache.tdb is denying permission. Should I have run the smbtree command in sudo?
    The hamachi interfaces are fine. It's just ID'ing every interface available. It's normal to not have permission to genache.tdb. This is not a failure; just info.

    I suggest we add a share to the configuration. How many different users (accounts) will be accessing a typical share? Do you really need a [homes] share or where you just trying to make something work.? The conventional place to store data is at /srv.
    -BAB1

  9. #29
    Join Date
    Jan 2011
    Location
    SoFla
    Beans
    44
    Distro
    Ubuntu 14.04 Trusty Tahr

    Re: Samba on Ubuntu 13.10

    [EDIT]
    Woah. It was just a matter of time. Now all the computers are showing up. Is it common for files and folders normally hidden in Windows to show in the Ubuntu machine's viewing of the Windows folders?
    [EDIT]

    Yup. I was just trying to get it to work first.

    Just before I read your last post I did some fiddling with the router settings and turned off the firewall, and voila, I was finally able to see "RAY_SERVER" in the Windows network, but there is still one slight little problem.

    When I browse the network in the Ubuntu machine it sees a location called 'Windows Network." Inside that folder is my "WORKGROUP." But now none of the Windows computers show up in there as they did before. The only thing that shows up in there is "RAY_SERVER."

    There are three different accounts for now that will be accessing the server share location. It is OK if it is at /srv as long as I can make organized folders under that. It would be best if each client (user) sharing has access to only its designated share area. On the other hand, I would like to be able to browse into each of the client's (user's) shared folders on the three clients from the Ubuntu machine. Each client Windows machine has essentially one major user (although I can go to the individual client stations and log in as administrator with full control).
    Last edited by ray_silva; April 6th, 2014 at 09:10 PM.

  10. #30
    Join Date
    May 2008
    Location
    SoCal
    Beans
    Hidden!
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: Samba on Ubuntu 13.10

    Quote Originally Posted by ray_silva View Post
    [EDIT]
    Woah. It was just a matter of time. Now all the computers are showing up. Is it common for files and folders normally hidden in Windows to show in the Ubuntu machine's viewing of the Windows folders?
    [EDIT]
    The short answer is: YES. All the computers are on the same LAN and will show up as they are discovered. It takes between 5 and 15 minutes for that to happen.
    Yup. I was just trying to get it to work first.

    Just before I read your last post I did some fiddling with the router settings and turned off the firewall, and voila, I was finally able to see "RAY_SERVER" in the Windows network, but there is still one slight little problem.
    Does this mean that the entire local LAN is unprotected from the Internet troublemakers? I have a firewall on my router that won't pass Windows browsing from the Internet. The local LAN has no restrictions at all.
    When I browse the network in the Ubuntu machine it sees a location called 'Windows Network." Inside that folder is my "WORKGROUP." But now none of the Windows computers show up in there as they did before. The only thing that shows up in there is "RAY_SERVER."
    That really should say "Windows TYPE Networks" Both Samba and Windows hosts will show up. The workgroups are only for visual separation. They have no other use.
    There are three different accounts for now that will be accessing the server share location. It is OK if it is at /srv as long as I can make organized folders under that. It would be best if each client (user) sharing has access to only its designated share area. On the other hand, I would like to be able to browse into each of the client's (user's) shared folders on the three clients from the Ubuntu machine. Each client Windows machine has essentially one major user (although I can go to the individual client stations and log in as administrator with full control).
    You as the administrator (via sudo) directly on the Ubuntu host can always see what is in all of the files on the entire machine.

    You can set up the shares as:
    • Public (all can create files and directories read and write to the files)
    • Private (only an authorized user can create files and directories read and write to the files)
    • Semi-Private ( only an authorized group can create files and directories read and write to the files)


    If you have different users on each windows machine you need to create the same named user account on Ubuntu and the same named Samba user account. In other words each user in the LAN needs a Windows, Ubuntu and Samba account, all with the same name. Once that infrastructure is set up we can begin. There is a specific method to add users to Ubuntu that you should use
    Code:
    sudo adduser <user_name>
    ...where <user_name> is by your choice. To add users to the Samba database you use this
    Code:
    sudo smbpasswd -a <user_name>
    ..always use the same individual password for both the Windows, Ubuntu and Samba user account.

    Is that enough info for you to add the users?

    Questions or concerns?
    Last edited by bab1; April 7th, 2014 at 12:01 AM.
    -BAB1

Page 3 of 4 FirstFirst 1234 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •