Windows 10: Samba Shares don't show up in Windows 10 Network

Very interesting thread. I myself have struggled with this issue for far to long. I believe the problem lies in Widows File Explorer view. I have been able to discover a workaround for at least my problem of not being able to browse to Linux Samba shares and truly it is only a workaround but it is simple enough for the average user to perform to get things useable in File Explorer.

A little background to the issue seems appropriate here so here goes. I have a total of 5 Win 10 installs at this time. I was in on the Insider program during the Win 10 development stage. I had no problem with preview builds of Win 10 prior to 10586 like many if not all others here. After the upgrade to 10586 as has been discussed here in great detail browsing to a Samba share became impossible. I still participate in the Insider program but I am on the slow track so have not upgraded yet to the latest build so I cannot say at this time if the issue being discussed here has been fixed or not.

Shortly after the release of Win 10 I upgraded 3 machines to Win 10, all Home versions and immediately noticed that it was now possible to browse my Samba server with File Explorer without issue. I was pleased to see this and figured problem solved. I still had the issue on my Insider install but did not think much of it as I had gotten so use to just typing in the server/share name to gain access it became second nature to do so. Over the holidays I embarked on a new machine build on which I installed the PRO version of Win 10 and immediately discovered that this install had the same issue of not being able to browse Samba shares. After way to much trial and error I finally found a way to work around the issue.

Workaround:
To have File Explorer display a Samba server and be able to browse the shares apply the following tweaks to File Explorer

Open File Explorer and click on the View tab. Now click on the Options and select Change folder and search options. From the resulting window in the Open File Explorer to field select This PC and click Apply. This will invoke a more familiar Win 7 style view in Explorer but you must close and reopen Explorer to see the results.

With a newly opened Explorer window click to select This PC in the menu in the left pane. Right click for a context menu and select Add a Network Location. This will start a Wizard to create a shortcut for a network location in File Explorer. Select Next and select Choose a custom network location then click Next. Now enter your servername/share or IP address to the share you wish to access (Example: //server/sharename). Click Next and enter a name for the short cut you are about to create and click Next. The wizard will now create a shortcut in the left menu with the name you chose and an icon will appear under Network showing your Samba server as an essentially Other Network Device.

Browse away.

Enjoy!

 

I have a network with 4 notebooks, 3 android mobiles, 2 WD external ethernet hard drive, 1 WDTV Live. After upgrade to Windows 10, when I click to "Network" (On Windows Explorer left panel), I can not see nothing. The computer can not see even itself. I have been searching in foruns and a lot of people are talking about this Windows 10 bug. I have tryed to configure the network using the router (DLink dir635) and the modem Humax. Nothing. The curious is: I have 3 notebooks with Windows 10. If I turn them all off and turn off the router, after turn on again, the first computer the see the shares, but the others can not. Other people talk in foruns about this problem. My problem is not only makes Windows 10 see My Cloud and My Book Live, but get back my home network Windows 10 get way. In the beginning, I thought the problem was with the Windows 10 version. I have one notebook Windows 10 (10240) that work perfectly well and two notebooks with Windows 10 (1511) that did not. After, I discover that, as I do not turn them off, the diference was not the Windows 10 version, but the fact the notebook with Windows 10 (10240) was the first turned on in the network. As I explained before, when I turn them all off, if I turn one notebook with Windows 10 (1511) [November Update] it will work perfectly well, but only the first turned on.

 

Have you tried to reboot your router? This often solves connection problems. Have you checked that the router firmware is up to date? This another thing that can get things working.

 

Yeah, that's because the Master Browser of the network seems to work properly with this bug. The first machine you turn on becomes the Master Browser if all the other machines are off.

 

Problem persists on Build 11102 :-(

 

Freshly installed Windows 10 Home 64bit on two different machines cannot connect reliably to my SMB shares. Various Androids and a Windows 7 PC can connect without issue.

I've already asked on superuser.com but didn't get any answer. Please don't mind that I post the issue here again:




At random the network drive connects, at 1 of 50 trials. I can browse my files for 10 seconds or so. Then it drops dead again..


Workgroup is correct. Sambauser has a username and password set on the server.


I tried:

• Adding "AllowInsecureGuestAuth" key to \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters
• Adding "server max protocol=SMB3" to smb.conf on the server
• Connecting with the ip like this "\\192.168.0.55\share"
• Disabling Network Adapter Power Saving
• Start Windows 10 in Diagnostic Mode
• Disable SMB2/3 in Windows, enable SMB1 https://support.microsoft.com/en-us/...ws-server-2012
• Adjust smb.conf further according to content in this thread
• Add the share as a "link" in File Explorer as a user previously described. Result is the same, this works at random for 10 seconds, then it's dead again

I carefully read through this topic but it didn't help.

If you know anything, please share.

 

What version of Windows 10 are you running. I have no issues with 1607 (anniversary) but even with a clean install of Creators Edition with NO other software installed the master browser is an issue. If I boot a 1607 computer first and it is the master browser, then I can see my CU edition but not if I boot the CU first. CU is plenty of nothing all happening all at once.

 

It may be because other devices are using port 139 and Windows 10 is now using port 445.

I have a public (no user/pass) Samba Share running on Remote Debian Stable Server which I have been accessing fine with Windows 10 for ages with the UNC path:

\\server.com\share (and file shortcuts etc)

But recently (around Windows Creator update i think) that path is timing out giving same error as forum user: irgendwer.

Event Viewer logs this after the timeout (20-30s):

Event Viewer->Application & Service Logs->Microsoft->Windows->SMBClient->Connectivity
Code: Failed to establish a network connection. Error: Device Timeout The specified I/O operation on %hs was not completed before the time-out period expired. Server name: server.com Server address: 12.34.56.78:445 (i changed the ip for privacy) Instance name: \Device\LanmanRedirector Connection type: Wsk Guidance: This indicates a problem with the underlying network or transport, such as with TCP/IP, and not with SMB. A firewall that blocks TCP port 445, or TCP port 5445 when using an iWARP RDMA adapter, can also cause this issue.[/quote] Turns out Windows 10 SMBClient tries to connect to remote SMB server on TCP port 445, and now (not sure if before they were or not) my ISP is blocking outgoing TCP port 445!! - Possibly because of cyber security threats like WannaCry.

My Samba server listens on 139 and 445 by default, and I can connect to it's 139 using telnet, but I cannot make Windows SMBClient use port 139, people say you cannot. Even trying specify port in UNC path etc (apparently \\server.com@port\share converts it to WebDAV).

So I am not sure WHAT changed (Windows or my ISP or both etc) but basically I think I am screwed Samba wise as Windows is locked to 445 and ISP is blocking it lol, I even tried a TCP port relay on my localhost:445->server.com:139 but of course Windows System process is listening on 445 so I cannot bind, attempts to disable 'server' and netbt left the port listening etc and I'm not wasting any more time on it.

I'll probably switch to WebDAV/NFS or SFTP Net Drive (pretty cool BTW, better than swish) or something, but I'm subscribing here in case any of you figure it out, good luck, especially to irgendwer, he seems to have tried everything!

 

Well, after having this problem resolved for a long time by disabling SMB2/3 and enabling SMB1, the problem is now back on Windows 10 Pro version 1709, build 16299.192. The problem, again, is as follows:

I run a Linux server using Samba 4.3.11. If I open the Windows 10 file explorer and click on Network, I cannot see the server. The icon for the server doesn't show up. However, I can type directly in the Explorer path box, '\\MYSERVERNAME\ShareName' and I can access the shares manually. The problem is that it doesn't find the name of the server on its own. Since I use my server for automatic backups, this causes a problem with that.

 

I have found that a number of problems with SMB resource publication can be solved by disabling the "HomeGroup Provider" service and setting "Function Discovery Resource Publication" to automatic. I don't know if it's germaine to your problem, as my problem was with discovery of other Windows 10 machines over SMB2/3 with SMB1 disabled, but all sorts of Windows machines started showing up properly when I disabled the HomeGroups service and made resource publication a default. HomeGroups seem to mess up regular LANManager (SMB) shares sometimes.

Let me know if this helps.

 

Hi folks

I've posted on this before

However to get the whole thing working have a look at my post on another thread

Finally SAMBA problems fixed for W10 plus access to Non Windows - Windows 10 Forums

Cheers
jimbo

 

From your link:

"Enable ALL the SMB V1 items not just the top 3, AND enable the SMB direct - both in Turn Windows on and off"
Where do I do this at? "top 3"? Where are these items?

 

From your link:

"Enable ALL the SMB V1 items not just the top 3, AND enable the SMB direct - both in Turn Windows on and off"

Where do I do this at? "top 3"? Where are these items?

 

That worked. As you said, taking those actions on those two services caused my shared servers to show up immediately.

 

I don't know if it's sabotage or incompetence, but HomeGroup is awful if you're using LANMan shares. Glad it worked!