Page 1 of 4 123 ... LastLast
  1.    22 Nov 2015 #1

    Samba Shares don't show up in Windows 10 Network


    I have a peculiar Samba share issue.

    I was running Windows 7 on my laptop. I have a file server running Linux and Samba. When I open the Network icon in Windows 7, I see my server there and I can open it and access the associated folder shares.

    I upgraded to Windows 10. Now if I double click the network icon, I don't see any machines except my local client laptop. However, if I enter the UNC path to my samba server (\\myserver) into the path bar of Windows Explorer, I can access the server. If I want to add a network printer to my laptop that is shared by the server, it won't find the server in the search list. However, I can enter the literal UNC path to the printer and add it. So it has something to do with nmb I think? Not sure.

    Any suggestions on how to resolve it?
      My System SpecsSystem Spec


  2. Joined : May 2015
    Central IL
    Posts : 3,059
    EL Capitan
       23 Nov 2015 #2

    What version of Linux are you using and what version of Samba? Try using system-config-samba if running a Ubuntu based distro. All computers need to be so that the workgroup is named "WORKGROUP". Normally I send people over to the proper Linux forum for this kind of stuff, because I was too busy with work. Now that I am retired, I have a lot of time available to help.

    Post your smb.conf before you make any changes, post a screenshot of your shares in the Samba Server Config tool. Then post the changes that you made with the tool that shows that they are working. Also make sure you go in and remove the ; in the Browseable line for the share.

    You can check for windows shares in Windows cmd with net view should show all computers on your network.
      My System SpecsSystem Spec

  3.    23 Nov 2015 #3

    Yeah , check your workgroup names match...I had this once too...took a little while to realise that was the issue/
      My System SpecsSystem Spec


  4. Joined : May 2015
    Central IL
    Posts : 3,059
    EL Capitan
       23 Nov 2015 #4

    Wullail said: View Post
    Yeah , check your workgroup names match...I had this once too...took a little while to realize that was the issue/
    Actually with the current version of Samba, you can get away with different workgroup names. There are some registry changes in windows that some people have to use to get the computer running Linux to see that computer.

    The one tool that does come in handy is WinSCP on a Windows computer to go in and make changes from the Windows computer as the Linux Root on the computer running Linux. Very handy if the computers are in different parts of the house.
      My System SpecsSystem Spec

  5.    23 Nov 2015 #5

    Version of Linux is Fedora 17. smbd and nmbd version 3.6.12-1.fc17.

    This was all working fine under Windows 7 Professional until I did the free upgrade to Windows 10 Pro this week. My workgroup is consistent and hasn't been changed. I have my Windows 10 client workgroup setup as before, with Windows 7, and it matches the server.

    Also, to reiterate, I can access the shares literally by entering the UNC path in Windows Explorer, or when selecting a printer. Windows 10 is just unable to browse to find the shares. So the shares are accessible, but names not being made known.

    My smb.conf file follows (shares at the end have been omitted - but an example is shown):
    Code:
    #======================= Global Settings =====================================
    
    [global]
    
    # ----------------------- Network-Related Options -------------------------
    #
    # workgroup = the Windows NT domain name or workgroup name, for example, MYGROUP.
    #
    # server string = the equivalent of the Windows NT Description field.
    #
    # netbios name = used to specify a server name that is not tied to the hostname.
    #
    # interfaces = used to configure Samba to listen on multiple network interfaces.
    # If you have multiple interfaces, you can use the "interfaces =" option to
    # configure which of those interfaces Samba listens on. Never omit the localhost
    # interface (lo).
    #
    # hosts allow = the hosts allowed to connect. This option can also be used on a
    # per-share basis.
    #
    # hosts deny = the hosts not allowed to connect. This option can also be used on
    # a per-share basis.
    #
    # max protocol = used to define the supported protocol. The default is NT1. You
    # can set it to SMB2 if you want experimental SMB2 support.
    #
            workgroup = MYWORKGROUP
            server string = Samba Server Version %v on Foo
    
            map to guest = Bad Password
            passwd program = /usr/bin/passwd %u
            passwd chat = *ew*password* %n\n *ew*password* %n\n *success*
            unix password sync = Yes
            admin users = root, moe
            guest ok = Yes
            hosts allow = 127.0.0.1, 192.168.1., 192.168.0.
    
            ;netbios name = Foo
    
    ;       interfaces = lo eth0 192.168.12.2/24 192.168.13.2/24
    ;       hosts allow = 127. 192.168.12. 192.168.13.
    
    ;       max protocol = SMB2
    
    # --------------------------- Logging Options -----------------------------
    #
    # log file = specify where log files are written to and how they are split.
    #
    # max log size = specify the maximum size log files are allowed to reach. Log
    # files are rotated when they reach the size specified with "max log size".
    #
    
            # log files split per-machine:
            log file = /var/log/samba/log.%m
            # maximum size of 50KB per log file, then rotate:
            max log size = 50
    
    # ----------------------- Standalone Server Options ------------------------
    #
    # security = the mode Samba runs in. This can be set to user, share
    # (deprecated), or nerver (deprecated).
    #
    # passdb backend = the backend used to store user information in. New
    # installations should use either tdbsam or ldapsam. No additional configuration
    # is required for tdbsam. The "smbpasswd" utility is available for backwards
    # compatibility.
    #
    
            security = user
            passdb backend = tdbsam
    
    # ----------------------- Domain Members Options ------------------------
    #
    # security = must be set to domain or ads.
    #
    # passdb backend = the backend used to store user information in. New
    # installations should use either tdbsam or ldapsam. No additional configuration
    # is required for tdbsam. The "smbpasswd" utility is available for backwards
    # compatibility.
    #
    # realm = only use the realm option when the "security = ads" option is set.
    # The realm option specifies the Active Directory realm the host is a part of.
    #
    # password server = only use this option when the "security = server"
    # option is set, or if you cannot use DNS to locate a Domain Controller. The
    # argument list can include My_PDC_Name, [My_BDC_Name], and [My_Next_BDC_Name]:
    #
    # password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name]
    #
    # Use "password server = *" to automatically locate Domain Controllers.
    
    ;       security = domain
    ;       passdb backend = tdbsam
    ;       realm = MY_REALM
    
    ;       password server = <NT-Server-Name>
    
    # ----------------------- Domain Controller Options ------------------------
    #
    # security = must be set to user for domain controllers.
    #
    # passdb backend = the backend used to store user information in. New
    # installations should use either tdbsam or ldapsam. No additional configuration
    # is required for tdbsam. The "smbpasswd" utility is available for backwards
    # compatibility.
    #
    # domain master = specifies Samba to be the Domain Master Browser, allowing
    # Samba to collate browse lists between subnets. Do not use the "domain master"
    # option if you already have a Windows NT domain controller performing this task.
    #
    # domain logons = allows Samba to provide a network logon service for Windows
    # workstations.
    #
    # logon script = specifies a script to run at login time on the client. These
    # scripts must be provided in a share named NETLOGON.
    #
    # logon path = specifies (with a UNC path) where user profiles are stored.
    #
    #
    ;       security = user
    ;       passdb backend = tdbsam
    
    ;       domain master = yes
    ;       domain logons = yes
    
            # the following login script name is determined by the machine name
            # (%m):
    ;       logon script = %m.bat
            # the following login script name is determined by the UNIX user used:
    ;       logon script = %u.bat
    ;       logon path = \\%L\Profiles\%u
            # use an empty path to disable profile support:
    ;       logon path =
    
            # various scripts can be used on a domain controller or a stand-alone
            # machine to add or delete corresponding UNIX accounts:
    
    ;       add user script = /usr/sbin/useradd "%u" -n -g users
    ;       add group script = /usr/sbin/groupadd "%g"
    ;       add machine script = /usr/sbin/useradd -n -c "Workstation (%u)" -M -d /nohome -s /bin/false "%u"
    ;       delete user script = /usr/sbin/userdel "%u"
    ;       delete user from group script = /usr/sbin/userdel "%u" "%g"
    ;       delete group script = /usr/sbin/groupdel "%g"
    
    
    # ----------------------- Browser Control Options ----------------------------
    #
    # local master = when set to no, Samba does not become the master browser on
    # your network. When set to yes, normal election rules apply.
    #
    # os level = determines the precedence the server has in master browser
    # elections. The default value should be reasonable.
    #
    # preferred master = when set to yes, Samba forces a local browser election at
    # start up (and gives itself a slightly higher chance of winning the election).
    #
    ;       local master = no
    ;       os level = 33
    ;       preferred master = yes
    
    #----------------------------- Name Resolution -------------------------------
    #
    # This section details the support for the Windows Internet Name Service (WINS).
    #
    # Note: Samba can be either a WINS server or a WINS client, but not both.
    #
    # wins support = when set to yes, the NMBD component of Samba enables its WINS
    # server.
    #
    # wins server = tells the NMBD component of Samba to be a WINS client.
    #
    # wins proxy = when set to yes, Samba answers 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.
    #
    # dns proxy = when set to yes, Samba attempts to resolve NetBIOS names via DNS
    # nslookups.
    
    ;       wins support = yes
    ;       wins server = w.x.y.z
    ;       wins proxy = yes
    
    ;       dns proxy = yes
    
    # --------------------------- Printing Options -----------------------------
    #
    # The options in this section allow you to configure a non-default printing
    # system.
    #
    # load printers = when set you yes, the list of printers is automatically
    # loaded, rather than setting them up individually.
    #
    # cups options = allows you to pass options to the CUPS library. Setting this
    # option to raw, for example, allows you to use drivers on your Windows clients.
    #
    # printcap name = used to specify an alternative printcap file.
    #
    
            load printers = yes
            cups options = raw
    
    ;       printcap name = /etc/printcap
            # obtain a list of printers automatically on UNIX System V systems:
    ;       printcap name = lpstat
    ;       printing = cups
    
    # --------------------------- File System Options ---------------------------
    #
    # The options in this section can be un-commented if the file system supports
    # extended attributes, and those attributes are enabled (usually via the
    # "user_xattr" mount option). These options allow the administrator to specify
    # that DOS attributes are stored in extended attributes and also make sure that
    # Samba does not change the permission bits.
    #
    # Note: These options can be used on a per-share basis. Setting them globally
    # (in the [global] section) makes them the default for all shares.
    
    ;       map archive = no
    ;       map hidden = no
    ;       map read only = no
    ;       map system = no
    ;       store dos attributes = yes
    
    
    #============================ Share Definitions ==============================
    [Attic]
            comment = Attic on My PC
            path = /foo/Attic
            valid users =moe, larry, curly
            read list = moe, larry, curly
            write list = moe
            read only = No
      My System SpecsSystem Spec


  6. Joined : May 2015
    Central IL
    Posts : 3,059
    EL Capitan
       23 Nov 2015 #6

    Smbd and nmbd are not two different things. Just call it Samba. Fedora is a PITA when it comes to this area. Ubuntu based distros are better supported, because they are Debian base and pretty much work right off of the bat.

    Linux Mint is what I use, and have zero problems with sharing.

    You may have to look on the Ubuntu forum to see if anyone else is having issues.

    I was playing around with BSD & Centos the other week. Both of them had issues with my wife's laptop running 10.

    Cannot Connect to CIFS / SMB / Samba Network Shares Shared Folders in Windows 10 - Tech Journey

    Looks like it may be related to the didabling of the Guest account in Windows 10.

    I did go into my wife's and set her shares to make permission under "Everyone", which has worked.

    A three year old thread, but still good info. [SOLVED] FC17, Samba, Browsing Windows Shares not accessible - FedoraForum.org

    Try the latest version of Fedora. Or just use Linux Mint.
    Last edited by bro67; 24 Nov 2015 at 00:19.
      My System SpecsSystem Spec


  7. Joined : May 2015
    Central IL
    Posts : 3,059
    EL Capitan
       23 Nov 2015 #7

    Your smb.conf is hosed up. That is part of the problem.
      My System SpecsSystem Spec

  8.    23 Nov 2015 #8

    bro67 said: View Post
    Your smb.conf is hosed up. That is part of the problem.
    Could you be a bit more specific?

    I could imagine there may be some oddities since it's a morph of my earliest config since I started using Linux and Samba from the early days of Redhat, pre-Fedora, when I had to build my own kernel, etc. But it always has worked fine until now, as it's pretty basic. Like I've said, Windows 7 as a client has no problem with it. I'm not using domain logins or proxies or anything exotic. What I do rely on is my Samba credentials matching my Windows client credentials (Windows 10 initially coercing me down the path of Microsoft could credentials messed me up initially, but I resolved that).
    Last edited by mbratch; 23 Nov 2015 at 12:52.
      My System SpecsSystem Spec

  9.    23 Nov 2015 #9

    bro67 said: View Post
    Smbd and nmbd are not two different things. Just call it Samba. Fedora is a PITA when it comes to this area. Ubuntu based distros are better supported, because they are Debian base and pretty much work right off of the bat.
    Yes, I understand. But they are two different services in Linux, so I mentioned them that way, especially since my issue seems to be related to the nmbd side of things.

    Linux Mint is what I use, and have zero problems with sharing.

    You may have to look on the Ubuntu forum to see if anyone else is having issues.
    I'll check the Fedora forum. I also have a Linux Mint machine and a Linux Ubuntu Studio machine on the network that I don't normally share from. I can try these as an experiment, though.

    Cannot Connect to CIFS / SMB / Samba Network Shares Shared Folders in Windows 10 - Tech Journey

    Looks like it may be related to the disabling of the Guest account in Windows 10.
    I'll check this. But at first blush, that thread looks like it's discussing an inability to connect. My server connects as long as I do it manually with the UNC.

    I did go into my wife's and set her shares to make permission under "Everyone", which has worked.
    I can explore permissions to see what that does.

    I'll check that out as well.

    Try the latest version of Fedora. Or just use Linux Mint.
    Hoping not to have to do this as it would be a PITA to get everything on my server validated. It's also a development machine for other projects so tools need to be revalidated, etc. I'm assuming and hoping that my problem really is just a configuration issue of some kind.
    Last edited by mbratch; 23 Nov 2015 at 12:48.
      My System SpecsSystem Spec

  10.    23 Nov 2015 #10

    Well, I finally found the problem, which is described in this link.

    Windows 10 will try to negotiate SMB3_11, which Samba4 doesn't yet support except in the current 4.3 release candidate. I suspect for now disabling SMB2/3 on the Windows 10 client is your best, if not ideal, option.

    Instructions for doing this can be found here:

    https://support.microsoft.com/en-us/kb/2696547
    I followed the directions for disabling SMB2/3 and enabling SMB1 (evidently you can't just enable SMB2), and my shares because visible immediately after I rebooted my Windows 10 client. I'll probably install the Samba 4.3 release candidate to get back to using SMB3_11.

    The odd thing is that not only did my Samba server show up after making this change, but my wife's Windows 8 laptop started to show up (and didn't before). So evidently, Windows 8 client wasn't happy about SMB3_11 either.
      My System SpecsSystem Spec


 
Page 1 of 4 123 ... 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 10:22.
Find Us
Twitter Facebook Google+



Windows 10 Forums