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

Page 4 of 5 FirstFirst ... 2345 LastLast
  1.    06 Jan 2016 #31

    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.
      My ComputerSystem Spec


  2. Posts : 8
    Windows 10 1703
       27 Jan 2016 #32

    persiomenezes said: View Post
    it will work perfectly well, but only the first turned on.
    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.
      My ComputerSystem Spec


  3. Posts : 21
    Windows 10 (10240), Windows 10 (1511)
       31 Jan 2016 #33

    Problem persists on Build 11102 :-(
      My ComputerSystem Spec

  4.    21 Apr 2017 #34

    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:
    Click image for larger version. 

Name:	error.png 
Views:	38 
Size:	10.3 KB 
ID:	131180

    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.
      My ComputerSystem Spec


  5. Posts : 5
    Windows 10x64 Pro
       20 May 2017 #35

    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.
      My ComputerSystem Spec

  6.    24 Jun 2017 #36

    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.
    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!
      My ComputerSystem Spec

  7.    07 Jan 2018 #37

    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.
      My ComputerSystem Spec


  • Posts : 8
    Windows 10 1703
       07 Jan 2018 #38

    mbratch said: View Post
    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.
      My ComputerSystem Spec

  •    07 Jan 2018 #39

    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
      My ComputerSystem Spec

  •    07 Jan 2018 #40

    jimbo45 said: View Post
    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?
      My ComputerSystem Spec


  •  
    Page 4 of 5 FirstFirst ... 2345 LastLast

    Related Threads
    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...
    Solved Can't access Samba shares on 10049 in Network and Sharing
    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...
    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 Samba Problems Please Help in Network and Sharing
    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,...
    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...
    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 12:52.
    Find Us