Page 2 of 4 FirstFirst 1234 LastLast
  1.    24 Nov 2015 #11
    Join Date : May 2015
    Central IL
    Posts : 4,228
    Mac OS Sierra

    Microsoft has not kept up with Samba with their SMB/CIFS. Even when they used Samba as the base for the code that runs Storage Spaces, they still never got it right. Especially that the majority of Enterprises run a lot of their servers on Linux.

    I went with the Amazon Unlimited for $60 a year, so that if I do have to blow away one of my two machines because of problems, I have all of my file data stored outside of the network.

    As for your Samba Config file. If you have been just upgrading without adjusting the config file over the changing of the Distro's, they tend to get screwed up. I keep a generic copy of the Samba Config file, so that if something does happen, I still have the out of the box code.

    The Samba Black Bible comes in really handy for the hard part of working with the config file. Now you can use Webmin for making changes to the Samba Config file. I use it for those times that I need to go in and check something on my computer, that is not readily easy to find through normal ways.
      My ComputerSystem Spec
  2.    24 Nov 2015 #12
    Join Date : May 2015
    Central IL
    Posts : 4,228
    Mac OS Sierra

    This is what my Samba Config file looks like. The only changes have been adding the Folder Shares.

    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. 
    
    
    #======================= 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, Linux Mint)
    
    
    # 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@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
        username map = /etc/samba/smbusers
        security = user
    ;    encrypt passwords = yes
    ;    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 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
    
    
    [Box]
        comment = Greg Box directory
        path = /home/gz7916/Box
        writeable = yes
        browseable = yes
        guest ok = yes
    
    
    [Downloads]
        comment = Greg Downloads
        path = /home/gz7916/Downloads
        writeable = yes
        browseable = yes
        guest ok = yes
    
    
    [Pictures]
        comment = Greg Pictures Directory
        path = /home/gz7916/Pictures
        writeable = yes
        browseable = yes
        guest ok = yes
    
    
    [Public]
        comment = Greg Public Shares
        path = /home/gz7916/Public
        writeable = yes
        browseable = yes
        guest ok = yes
      My ComputerSystem Spec
  3.    24 Nov 2015 #13
    Join Date : Nov 2015
    Webster, NY
    Posts : 46
    Windows 10
    Thread Starter

    Quote Originally Posted by bro67 View Post
    Microsoft has not kept up with Samba with their SMB/CIFS. Even when they used Samba as the base for the code that runs Storage Spaces, they still never got it right. Especially that the majority of Enterprises run a lot of their servers on Linux.
    I actually think it's the other way around. Windows 10 now uses SMB3, which Samba has not kept up with (according to the link I found). The latest stable build of Samba, though, does support it. My Ubuntu 14.10 machine, which is a very recent Ubuntu version, is at Samba 4.1, but it's 4.2 that has SMB3 support. With similar issues being reported (like this one), Microsoft may be having problems using SMB3 between it's own systems. Microsoft created SMB (Server Message Block)/CIFS, after which Linux came up with "Samba" to provide a compatible system to enable Linux servers/clients to play properly on Windows networks. A fun fact: the name "Samba" was derived by looking up a word in the Linux spelling dictionary matching the regex, "s*m*b*".

    As for your Samba Config file. If you have been just upgrading without adjusting the config file over the changing of the Distro's, they tend to get screwed up. I keep a generic copy of the Samba Config file, so that if something does happen, I still have the out of the box code.
    I have done the same. I kept the "generic" config file template. To be clearer, what I would do is edit the newer smb.conf file that was installed on Fedora upgrades to be consistent with the settings in my prior version. I'm still not sure why you said my smb.conf file is "hosed". I would like to know specifically what's wrong with it. It doesn't really have anything exotic going on.

    The Samba Black Bible comes in really handy for the hard part of working with the config file. Now you can use Webmin for making changes to the Samba Config file. I use it for those times that I need to go in and check something on my computer, that is not readily easy to find through normal ways.
    Great tip, thanks!
    Last edited by mbratch; 24 Nov 2015 at 08:46.
      My ComputerSystem Spec
  4.    24 Nov 2015 #14
    Join Date : May 2015
    Central IL
    Posts : 4,228
    Mac OS Sierra

    Samba has kept up. It is Microsoft who is lagging behind. All versions of Samba are backwards compatible. Windows has never worked right with Samba as far back with XP, without doing the registry edit and changing the settings in Windows in Advance Sharing, to not use Homegroup, but the second choice.

    Samba writes the code, along with others who contribute. But because Microsoft Sales wants to force everyone to use Sharepoint, etc. as their server product, even though a typical home user does not need a server.

    It used to be with Samba 3.x.x, you had to use Capital letters for your username, no special characters or mix of upper and lower case letters. That was because Windows did not comprehend that info.
      My ComputerSystem Spec
  5.    25 Nov 2015 #15

    Hi there

    I'm running CENTOS 7 -- no problem connecting to Windows from CENTOS - should work also on other distros

    1) use smbpasswd to add your user - use the user you have on windows
    2) in the GLOBAL settings of the samba config file get your netbiosname set correctly. note This is for HOME networks - I'm not using logon domains etc. simply computers on a home LAN.


    [global]
    workgroup = WORKGROUP
    passdb backend = smbpasswd
    preferred master = yes
    printing = cups
    printcap name = cups
    printcap cache time = 750
    cups options = raw
    map to guest = Bad User
    usershare allow guests = Yes
    server string = ""
    usershare max shares = 100
    usershare owner only = false
    netbios name = gylfi
    wins support = no
    name resolve order = bcast host lmhosts wins

    Now using Dolphin or whatever you'll be able to see the machines and just double click on the Windows machine. A login popup will be displayed - enter your (Windows) username and password and you'll have access to all the shares - ensure the drives / directories are shared.

    The other way round - from Windows to Linux should be no problem provided you've added the shares in the rest of the samba configuration file.

    Note also if you have a firewall enabled in Linux allow outbound and inbound connections for SAMBA ports. Same applies for Windows connections too. Check firewall settings.

    Cheers
    jimbo
      My ComputerSystem Spec
  6.    26 Nov 2015 #16
    Join Date : Nov 2015
    Posts : 11
    Windows 10

    Quote Originally Posted by mbratch View Post
    I actually think it's the other way around. Windows 10 now uses SMB3, which Samba has not kept up with (according to the link I found). The latest stable build of Samba, though, does support it. My Ubuntu 14.10 machine, which is a very recent Ubuntu version, is at Samba 4.1, but it's 4.2 that has SMB3 support.
    I guess I'm having a conceptual problem with this "fix" of disabling smb2/smb3 in Windows.

    I have an Ubuntu 14.04 machine with Samba at 4.1.6. Browsing for shares from Explorer does not work for me either but I can access the Ubuntu machine directly from Run ( Win Key + R ) with ( in my case ) a
    Code:
    \\bart\Downloads
    And the connection is made and I can access the share.

    If I open the powershell as administrator and run Get-SmbConnection to get the details of this connection I get this:

    PS C:\WINDOWS\system32> Get-SmbConnection

    ServerName ShareName UserName Credential Dialect NumOpens
    ---------- --------- -------- ---------- ------- --------
    bart Downloads WIN10\morbius MicrosoftAccount\XXXX@YYYY.com 3.0 1
    Windows 10 is connecting to my samba server using version 3.0 of SMB.

    I don't think this is a samba version problem I think it's a more complicated issue from this Function Discovery process that Explorer now uses to "browse for" or "discover" hosts on the network.

    We got the attention of a Microsoft employee in this thread so one hopes it will eventually get fixed:
    Cannot connect to CIFS / SMB / Samba Network Shares Shared Folders in Windows 10 after update 1511/10586


      My ComputerSystem Spec
  7.    26 Nov 2015 #17
    Join Date : Aug 2015
    Posts : 12
    Windows 10 Pro

    I removed netbios from my samba file share,
    added this to my smb.conf
    disable netbios = yes
    smb ports = 445
    and can now connect with no problems using \\ip or \\hostname as long as you add the host name to your windows host file.
      My ComputerSystem Spec
  8.    26 Nov 2015 #18
    Join Date : Nov 2015
    Posts : 11
    Windows 10

    You don't even have to mess with a host file. Windows 10 has joined the 21st century and speaks mDNS / DNS-SD ( Avahi in Linux / Bonjour in OSX ).

    You can access a Linux or OSX machine by it's hostname and a ".local" TLD. So in my example above I would access my Ubuntu machine with a:
    Code:
    \\bart.local\Downloads
    Not more netbios, workgroups, name resolve order changes, 15 character host name length restrictions, etc... It's also way faster at connecting.

    The only thing Windows didn't do is take this to it's logical conclusion. Both OSX and Linux can "announce" to the network that they are a samba server using dns-sd. All other Linux and OSX machines will see them immediately under their respective Networks. Windows cannot do that - yet.
      My ComputerSystem Spec
  9.    26 Nov 2015 #19
    Join Date : Aug 2015
    Posts : 138
    Microsoft Windows 10 Pro 64-bit BETA

    Quote Originally Posted by morbius1 View Post
    You don't even have to mess with a host file. Windows 10 has joined the 21st century and speaks mDNS / DNS-SD ( Avahi in Linux / Bonjour in OSX ).

    You can access a Linux or OSX machine by it's hostname and a ".local" TLD. So in my example above I would access my Ubuntu machine with a:
    Code:
    \\bart.local\Downloads
    Not more netbios, workgroups, name resolve order changes, 15 character host name length restrictions, etc... It's also way faster at connecting.

    The only thing Windows didn't do is take this to it's logical conclusion. Both OSX and Linux can "announce" to the network that they are a samba server using dns-sd. All other Linux and OSX machines will see them immediately under their respective Networks. Windows cannot do that - yet.
    You seem to know these things. Perhaps you can help?
    I have one Win10 x64, two Win7 x64, one OSX Captan and one WD MyCloud NAS connected to the network.
    On Win10 x64 v10240 all c's could see each other and the NAS in the "networkbrowser", I could access all from all. Homegroup is disabled. After the Win10 x64 10586 upgrade the OSX and the NAS completely disappeared from the Win10 machine. I have managed to make the NAS flash by once by disabling and the enabling networkdiscovery on the Win10 machine. All shares are reachable by name. Can you help?
      My ComputerSystem Spec
  10.    26 Nov 2015 #20
    Join Date : Nov 2015
    Posts : 11
    Windows 10

    Build 10586 is when everything broke in Win10 Network discovery. I am like you. I can access everything on my network as long as I ask for it by name.

    That is what this TechNet thread is about : Cannot connect to CIFS / SMB / Samba Network Shares Shared Folders in Windows 10 after update 1511/10586



      My ComputerSystem Spec

 
Page 2 of 4 FirstFirst 1234 LastLast


Similar Threads
Thread Forum
Cannot connect to SAMBA shares on CENTOS7
Hello everyone, I'm having this very annoying issue with samba shares. The server is running on a CentOS 7 distro with samba-4.1.12-23.el7_1.x86_64. My Windows 10 build is 10240. The shares are visible but when I try to connect it waits a...
Network and Sharing
Solved Can't access Samba shares on 10049
I just reinstalled after I was having issues. Everything seems to be working smoothly, except that I can't access the shares on all but one of my other computers for some reason. Most devices that aren't running either some flavor of Windows or...
Network and Sharing
Solved Unable to map Network Shares Windows 10
Hi, I've got 2 Western Digital Network drives hard wired on my network, a My Book World and an EX2. Since upgrading to Windows 10 I've had intermittent problems viewing and setting network drives. I've read a lot of other posts and tried a...
Network and Sharing
Network Samba Problems Please Help
ok here is my situation. I reformatted clean install on my desktop. Had some hiccups but everything ok. I use in the living room this streaming box from element company,love this box. Anyway after i share with everyone this folder for movies,...
Network and Sharing
Build 10041 Samba doesn't show C drive properly !!!!
Hi there 3 Linux servers with different distros seem to be unable to read the C drive directory properly on a new Windows 10041 (Real) machine. Seems to be NO problem in accessing the other shared drives on the computer. This problem only...
Network and Sharing
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 21:26.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums