Windows 10: 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?

:)

 

Windows 10 Network Computers missing on some computers (9 networked together)

Cannot connect to CIFS
SMB Samba Network Shares & Shared Folders in Windows 10 after update 1511 10586

That's the proper link to what I copy pasted.

 

Windows 10 November Update - cannot see other network devices

The most persistent news I have on these issues is that my Linux Samba server still does not show in the Network Neighborhood on the Windows 10 machines.

My home network (Workgroup) consists of 2 desktops, 1 laptop and 1 Surface Pro 3 all on the latest Windows 10 1511 build. And 1 Linux machine that I upgraded this week to Fedora 23 and Samba 4.3.1.

The Linux machine also serves as the WINS server and a VPN server. Thus offering remote access to the Windows based shares.

After the upgrading of the Windows machines several weird and peculiar connectivity problems turned up. Machines not showing, not able to connect to shares, printers (wired to the Linux machine) not reachable. Long waits on restoring persistent shares mapping
to drives.

I'd subsequently checked, reset and/or reconfigured all networking related settings like hostnames, workgroup name, protocol settings, etc.

End of the story is that everything is working as it should without any serious issues.

From the Linux machine I can access all the Windows based hosts and shares again. And all Windows 10 machines are shown to be part of the Windows Network.

Windows 10 machines now do show in each others Network Neighborhood. Persistent share to drive mappings work as a charm again. No gibberish output for nbtstat -r anymore. Also the Linux host, share and printers can be reached by name from all my machines
again.

I did not disable any SMB version setting anywhere. I do even expect everything is communicating based on the latest SMB v3.11 level which is supported by the now installed Samba 4.3.1.

Perhaps here a huge benefit having a home made Linux based 'NAS' which gives maximum flexibility in upgrading and configuring. Could be much different from NAS devices with much older Samba releases embedded.

As said. The only persisting minor issue is the Linux Samba server not being visible in the Windows 10 Network Neighborhood.

 

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.

 

Yeah , check your workgroup names match...I had this once too...took a little while to realise 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.

 

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[/quote]

 

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.

 

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).

 

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.

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.

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 can explore permissions to see what that does.

I'll check that out as well.

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.

 

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

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.

 

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.

 

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[/quote]

 

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*". *Smile

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.

Great tip, thanks!