Samba machine not showing in Network folder


  1. Posts : 4
    Windows 10
       #1

    Samba machine not showing in Network folder


    Not sure if here or the Ubuntu forums is the correct place to post this, so I'm posting to both.

    I have a file server running Ubuntu Server 14.04, with Samba set up for Windows file shares. I have it all set up to do mostly what I want, but there's one odd problem that I can't seem to fix: even though I can manually go to //192.168.1.3 (the IP) or //fileserver and browse my shares and files normally, I can't get the file server to show up in Windows' Network folder.

    No amount of refreshing the folder, restarting Samba, or rebooting either my computer or the file server seems to fix this. All that shows up is the machine I'm using, as well as whatever other Windows PCs are running (which means that network discovery is definitely set properly). Also, I can map network drives to the specific shares without an issue.

    I've confirmed that both machines are on the same workgroup (smb.conf has workgroup = WORKGROUP, and my Windows 10 machine is on WORKGROUP as well (and is stuck on that, too, since it's running 10 Home). Googling the issue showed other people with similar problems, and offered various config options in smb.conf as a solution, but none of them work. (I did of course restart Samba after each attempt.)

    This is my smb.conf, edited for privacy and to remove commented lines (it's mostly default):

    Code:
    [global]
    
    workgroup = WORKGROUP
    
    server string = <server string>
    
    dns proxy = no
    
    log file = /var/log/samba/log.%m
    
    max log size = 1000
    
    syslog = 0
    
    panic action = /usr/share/samba/panic-action %d
    
    server role = standalone server
    
    passdb backend = tdbsam
    
    obey pam restrictions = yes
    
    unix password sync = yes
    
    pam password change = yes
    
    map to guest = bad user
    
    [Share A]
    path = /home/fileserver/blah/blah
    read only = no
    writeable = yes
    browseable = yes
    create mask = 0770
    force create mode = 0770
    locking = yes
    
    [Share B]
    path = /home/fileserver/blah/blah
    read only = no
    writeable = yes
    browseable = yes
    create mask = 0770
    force create mode = 0770
    locking = yes
    
    Nothing but more shares with identical settings below here.
    Did I set something wrong or what?

    EDIT: I just noticed that it shows up like it should on my Surface RT's network folder, so the problem seems to be just on Windows' end on my main machine.
    Last edited by Roadsguy; 14 Jan 2016 at 10:15.
      My Computer


  2. Posts : 494
    Win 10 Pro x64 versions
       #2

    Problem is with Windows 10 networking. Apparently Win 10 does not broadcast NetBT over a LAN when searching for devices on the local network. What is being broadcast is WSD requests. This is causing a problem with devices reporting themselves which in turn means they are not discover-able. The best temporary fix I have found is to create a shortcut to the problem devices on those having the issue of not seeing them. This way you will have quick access to the devices and can delete the shortcuts once a fix has been released.
      My Computer


  3. Posts : 4
    Windows 10
    Thread Starter
       #3

    Railtech said:
    Problem is with Windows 10 networking. Apparently Win 10 does not broadcast NetBT over a LAN when searching for devices on the local network. What is being broadcast is WSD requests. This is causing a problem with devices reporting themselves which in turn means they are not discover-able. The best temporary fix I have found is to create a shortcut to the problem devices on those having the issue of not seeing them. This way you will have quick access to the devices and can delete the shortcuts once a fix has been released.
    Well that's pretty much what I've been doing in the meantime, as well as mapping network drives.

    Is the lack of NetBT requesting a known bug or a dropped feature?
      My Computer


  4. Posts : 138
    Microsoft Windows 10 Pro 64-bit BETA
       #4

    It's a bug in the SMB implementation introduced in v10586. It's fixed in the current insider preview and is scheduled for the public in March.
    Another workaround is to disable SMB 2/3 as the bug does not affect SMB1
      My Computer


  5. Posts : 494
    Win 10 Pro x64 versions
       #5

    Disabling SMB 2/3 can introduce other unwanted behavior, careful there.
      My Computer


  6. Posts : 1,936
    win 10 Insider
       #6

    DoItJust said:
    It's a bug in the SMB implementation introduced in v10586. It's fixed in the current insider preview and is scheduled for the public in March.
    Another workaround is to disable SMB 2/3 as the bug does not affect SMB1
    My NAS box is not on my network (being returned for warranty replacement) so can you please confirm both NAS and win shares are fine now with 11099?

    Certainly, the win shares seem OK on my network now both from 11099 AND 10586 comps. However, net view gives the 1231 error on the two 10586 comps but works OK on the two 11099 comps. However, if a 10586 is the master browser, net view is OK!

    Looks like some light at the end of the tunnel?
      My Computers


 

  Related Discussions
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 06:00.
Find Us




Windows 10 Forums