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

    Question

  • This started after update 1151/10586.
    Friday, November 13, 2015 2:37 PM

All replies

  • I can connect but the shares aren't shown in the Explorer. This is the case at least since build 10565 but I think also before that insider update. I wonder why nobody has seen this before. Everyone who uses a NAS or Linux server should remark this. If I put the path directly into the Explorer (e.G. \\nuc\data) it works also with 1511 alias build 10586. It isn't shown as share on the right side of Networks but on the left side (folders). This behavior is very strange to me and makes no sense. I think this a bug. Shame on you Microsoft. How can such thing happen?
    • Proposed as answer by Arfa uk Monday, November 23, 2015 9:49 PM
    • Unproposed as answer by Arfa uk Monday, November 23, 2015 9:50 PM
    Saturday, November 14, 2015 12:53 PM
  • and net view won't work anymore

    net view /all

    System error 1231 has occurred.

    The network location cannot be reached. For information about network troubleshooting, see Windows Help.

    Sunday, November 15, 2015 10:25 AM
  • And nbtstat -r produces gibberish:

    nbtstat -r

        NetBIOS Names Resolution and Registration Statistics
        ----------------------------------------------------

        Resolved By Broadcast     = 1
        Resolved By Name Server   = 0

        Registered By Broadcast   = 4
        Registered By Name Server = 0

        NetBIOS Names Resolved By Broadcast
    ---------------------------------------------
                       佇呒††††††

    As member jarau already stated it doesn't appear to be a name resolution problem since a \\hostname in explorer lists the host and it's shares as expected. It appears to be a network browsing or discovery problem.

    And it's only one way. My linux and osx systems can discover and access the Win10 system just fine.

    Sunday, November 15, 2015 1:51 PM
  • Same for me. Just update to the "new " version of Windows 10 (version 1511,10586,3). Cannot see anymore my NAS, but if i type the address (whateveritiscalled) it shows up. A shortcut on the desktop with the same address open the Windows and there i can see the NAS and all folders associated. Nothing that i have tried works to bring it up back. Maybe i will have to install user group (groupe résidentiel), and i do not like it !
    Sunday, November 15, 2015 3:16 PM
  • Can you provide more details and context of the behavior that you are seeing?

    1. Are these mapped network drives?
    2. Are you able to access the network share at all using \\ipaddress or \\hostname? If not, what is the error message that you receive?
    3. What profile do you have assigned to your network connection? Private, Public or Domain?
    4. Under Control Panel\Network and Internet\Network and Sharing Center\Advanced sharing settings, depending on profile assigned, is network sharing enabled?

    If everything above looks correct, capture a network trace and send to arudell at Microsoft dot com with title of this thread and your alias as the subject. Please provide me the IP address of your client machine and IP address of the destination device in your email.


    Adam Rudell | Sr Support Engineer | Windows Beta | Microsoft Corporation

    Monday, November 16, 2015 6:22 PM
  • I cannot browse some systems in Network, but my own system and a Windows 7 system are visible. This problem appeared before I performed the 1511 update but that update did not fix the problem. I'm on a working Domain network. A 2008r2 server and another Win10Pro system are not visible. I have spent about 5 hours troubleshooting including the following things which have not worked. 

    Ran the network troubleshooter.

    Disabled Windows and Norton Firewalls.

    Ran Tweaking.com's network repair tool.

    Removed and then reinstalled File and Printer Sharing and the Microsoft Client.

    Used both fixed IP address settings and DHCP.

    Restarted many times including the remote machines and the router.

    Removed and reinstalled the Realtek 1Gb Network adapter.

    Downloaded and installed the latest Realtek driver.

    Turned off Network Discovery in Domain, then turned it back on.

    Tried various MTUs from 576 to 1500.

    Weird thing is a nearly identical PC sitting 5 feet away with the same hardware and software works like a champ. I even compared settings in the \tcpip service using regedit. The other machines on the network can browse and see the non-working machine without any problems.

    Even though Network Discovery is turned ON in the Control Panel\All Control Panel Items\Network and Sharing Center\Advanced sharing settings area, I'm NOT seeing a setting in the "new" Ethernet properties dialog which controls "Finding" devices in that profile.

    The profiles showing in the Registry appear to be complete and corruption free and correctly set to "Domain" status.

    So I can see a Windows 7 Pro machine but not a Windows 10 Pro or a Server 2008R2 box.

    I can map a drive to the machines I can't "see" and it works fine. I can use File Explorer without a problem so long as I start the process by typing in \\machine_name in the address bar to get started.

    It's a stumper and I guess I've wasted enough time on it today.

    -Mike

    Monday, November 16, 2015 6:55 PM
  • And nbtstat -r produces gibberish:

    nbtstat -r

        NetBIOS Names Resolution and Registration Statistics
        ----------------------------------------------------

        Resolved By Broadcast     = 1
        Resolved By Name Server   = 0

        Registered By Broadcast   = 4
        Registered By Name Server = 0

        NetBIOS Names Resolved By Broadcast
    ---------------------------------------------
                       佇呒††††††

    As member jarau already stated it doesn't appear to be a name resolution problem since a \\hostname in explorer lists the host and it's shares as expected. It appears to be a network browsing or discovery problem.

    And it's only one way. My linux and osx systems can discover and access the Win10 system just fine.

      Indeed. My bridged Windows 7 & Win 8.1 virtual machines (VirtualBox and Hyper-V) can see and access the physical machines (including Win 10 ver 1511). Some of these Win 10 ver 1511 LAN machines cannot even see themselves!

     And yes, I also have garbage records in nbtstat -r output.


    Bill

    Tuesday, November 17, 2015 4:01 AM
  • I can connect but the shares aren't shown in the Explorer. This is the case at least since build 10565 but I think also before that insider update. I wonder why nobody has seen this before. Everyone who uses a NAS or Linux server should remark this. If I put the path directly into the Explorer (e.G. \\nuc\data) it works also with 1511 alias build 10586. It isn't shown as share on the right side of Networks but on the left side (folders). This behavior is very strange to me and makes no sense. I think this a bug. Shame on you Microsoft. How can such thing happen?

      You don't need to have a NAS or a Linux server to see it. I have it on an all Windows network without a NAS. NT-style computer browsing is completely stuffed.

     

    Bill

    Tuesday, November 17, 2015 4:07 AM
  • Same thing happened to me after update.

    In my case the reason was ethernet interface having lost all the protocls except ipv4 and ipv6.
    I added the net client, sharing and machine discovery related protocols and that solved all my issues.

    Possible reason was that I had Hyper-V active and lost all network connectivity in the update
    1511/10586 corrupting hyper-v networking.
    I recovered the connectivity by removing the hyper-v functionality and used network diagnostic.
    That only restored the Basic connectivity. All the additional protocol configs were on the removed hyper-v
    virtual interfaces.

    Tuesday, November 17, 2015 10:38 AM
  • shutdown all computers

    you may have to do this one computer at a time

    reset router

    HAD TO UNINSTALL AND INSTALL CLIENT FOR MICROSOFT NETWORKS AND FILE AND PRINT SHARING FOR MICROSOFT NETWORKS

     NETWORK AND SHARING>CHANGE ADAPTER SETTINGS>RIGHT CLICK ADAPTER>CHOOSE PROPERTIES>UNINSTALL CLIENT FOR MICROSOFT NETWORKS

    NETWORK AND SHARING>CHANGE ADAPTER SETTINGS>RIGHT CLICK ADAPTER>CHOOSE PROPERTIES>UNINSTALL FILE AND PRINT SHARING FOR MICROSOFT NETWORKS

    NETWORK AND SHARING>CHANGE ADAPTER SETTINGS>RIGHT CLICK ADAPTER>CHOOSE PROPERTIES>INTERNET PROTOCOL VERSION 4>INSTALL>CLIENT>INSTALL CLIENT FOR MICROSOFT NETWORKS

    NETWORK AND SHARING>CHANGE ADAPTER SETTINGS>RIGHT CLICK ADAPTER>CHOOSE PROPERTIES>INTERNET PROTOCOL VERSION 4>INSTALL>SERVICE>INSTALL FILE AND PRINT SHARING FOR MICROSOFT NETWORKS

    SHUTDOWN

    NET VIEW gives error 1231 !!

    Discovered that this new Windows build has magically become CASE SENSITIVE to machine names!!

    IF you have missing shares or completely disappeared machines on your LAN, make sure their machine names are not mixed-case. If they are mixed case, rename them to ALL CAPS and then reboot.

    Problem SOLVED, they will no longer be invisible on your network.

    Just posting this for the benefit of anyone else who may have machines that are ping-able, and have good  DNS name resolution, but it seems that NETBIOS resolution is 'somehow' broken, even though it is properly enabled. What I discovered today was that somehow the latest Win10 build has become slightly CASE-SENSITIVE - and this breaks the old NETBIOS standard going back to antiquity.

    So rename your "invisible" shares or machine names to UPPER-CASE, and they will magically appear on your WORKGROUP again.

    http://forum.synology.com/enu/viewtopic.php?f=49&t=106924

    sc.exe config lanmanworkstation depend= bowser/mrxsmb10/nsi
    sc.exe config mrxsmb20 start= disabled

    reboot


    Tuesday, November 17, 2015 1:24 PM
  • None of that makes any difference on my system. Perhaps it will for others.

    And just to reiterate - probably too many times here - it's not a netbios name resolution problem since I can ask for a host explicitly with a \\name and it will give me a list of all the shares on that host. It's that explorer > network cannot browse to and display "discovered" hosts.

    For what it's worth as part of the unwashed masses it really seems to be a problem with this "function discovery platform" thingy. It's supposed to go from protocol to protocol until it finds everything but somehow netbios is left out of the party.

    Right now my Win10 machine can not discover itself under Network. I can access it with a \\Win10 just fine. Yesterday it could see itself under Network but when it did the "Discovery Method" column in explorer showed "WSD" not "NetBIOS"

    Tuesday, November 17, 2015 6:53 PM
  • I found that starting the ‘Function Discovery Resource Publication’ service on each machine made them appear in the network folder list of machines that had been updated to Windows 10 / 10586, so I set that service to automatic startup. The other related service, ‘Function Discovery Provider Host’, seems to start when required, e.g. refreshing the network folder. I did not disable smb or rename machines to upper case.

    Nbtstat –r still produces garbage, and net view /all still produces system error 1231, but maybe those have been deprecated.

    Wednesday, November 18, 2015 9:14 PM
  • Regrettably that doesn't work for me either.

    Both services are already running on my Win10 machine yet I still can't see myself in explorer.

    And try as I might I can't seem to find either service on any of my Linux or OSX machines.

    Thursday, November 19, 2015 12:35 PM
  • I wanted to let everyone know on this thread that I have been able to reproduce the issue in my environment and I have logged an issue with the product group to have them take a look and provide feedback.

    I will update this thread again once I have some more information.


    Adam Rudell | Windows Networking Beta | Microsoft Corporation

    Thursday, November 19, 2015 6:02 PM
  •   Thanks Adam.

    Bill

    Friday, November 20, 2015 1:20 AM
  • Thanks. It WORKS for me. Just start ‘Function Discovery Resource Publication’ service, shut down the computer then restart and ......bam! all the NAS and shared folder and computer where back again.

    Thanhs again.

    Friday, November 20, 2015 1:40 PM
  •                      

    ledsd,

    Thanks! The sc.exe and all cap machine names solved the problem for me. I now have a no 1231 error Net View and File Explorer Network on both PCs showing my two computers.

    I created a thread in the Ms Community Windows 10 Networking and Internet PC regarding the aforementioned  network issue. In one of the replies, it was suggested to run netcfg  -d on each PC and reboot. I have not tried this, because sc.exe corrected the PC invisibility problem. 

    Finally, I am a retired IT professional (46 years). If I had been responsible for this network debacle, I would not have seen another day in IT. When will Microsoft learn?  

      
    • Edited by Allen305 Saturday, November 21, 2015 12:50 AM
    Saturday, November 21, 2015 12:42 AM
  • For what it is worth I found out the following:

    1) All shares can be accessed on all network pc's in file file explorer with \\192.168.0.xxx

    2) upper and lower case share names issue mentioned earlier is true if you connect to Linux based shares

    3) all share are visible on non-Windows pc's

    4) When I shut down all Windows pc's in the network and restart just one no matter which one all shares are shown in the Windows machine after some time. When I start additional ones only the Windows machines are show in the additional ones

    Monday, November 23, 2015 12:11 AM
  • Hi everyone,

    We had the same problem on Windows Surface with "Windows 10 Pro" - after upgrade to 1511 update CIFS folders on corporate network ware inaccesible to this machine.

    The other momentum was that user lost some new files in Documents folder (which syncs to that Network location when he arrives at office).  User created these files at home before applying 1511 update. There was no problem reported in Sync Center.


    Monday, November 23, 2015 1:47 PM
  • Same here I'm afraid. Synology NAS and FreeNas boxes no longer appear on network browse although they can still be seen if a shortcut to \\BOXname is made. It doesn't have to be uppercase to find it. Net view and nbtstat -r give the same errors as reported above.

    It may not be directly connected but this update also seems to have caused an inabililty to print to an old workhorse LaserJet 6MP connected by LPT1. Files get stuck in the spooler with Event ID 372 error code 2 - "the system cannot find the file specified" although it's clearly in the spool folder.  Thanks a bunch microsoft, it was all working very well before this.

    Monday, November 23, 2015 3:27 PM
  • I had these issues where I could not see any of my Workgroup NAS drives on 3 of my Windows 10 PC's.  I could see them OK from a PC that was running Linux Mint.  Strangely as soon as I turned off the Linux Mint PC and rebooted the Windows 10 PC's then all of my NAS drives were visible.  But as soon as I turned on the Linux Mint PC they all disappeared.  My solution was to stop running Samba on the Linux PC and now all NAS drives are visible both on Windows 10, Windows 7, XP and Linux Mint.  All my NAS drives/PC's belong to Windows Workgroup.  Also Net view works whereas before it was not.

    Monday, November 23, 2015 9:58 PM
  • I don't know if this provides any more clues as to what is going on but have just run ShareEnum from the Sysinternals suite on two WIndows 10  64-bit machines, both part of the same workgroup, one with the Threshold update and one without.  The pre-update machine lists all the appropriate shares on the network associated with the workgroup. including Synology NAS and FreeNas box.  The updated machine Just says "No domains or workgroups were found on your network". !!! I was looking for a copy of Microsoft's old BrowStat utility to check on what various machines think are the master browser, but it seems to have vanished.
    Tuesday, November 24, 2015 5:16 PM
  • I get the same result with ShareEnum.

    Network works great from a Vista machine! 

    C'mon, MS, you must know what has happened.

    Wednesday, November 25, 2015 3:06 AM

  • From my testing it looks like the computer that is the master browser can see the shares but the others can't get the shares from the master browser.

    In the event log/system on the problem comp I see a warning  source BROWSER ID 8021 "The browser service was unable to retrieve a list of servers from the browser master \\pcname on the network\Device\NetBT_Tcpip_(...........).

    Next there is a browser Information entry BROWSER id 8032 saying "The browser service has failed to retrieve the backup list too many times on transport \Device\NetBT_Tcpip_(...........). The backup browser is stopping".

    Can someone please check to see if you are getting these?
    Wednesday, November 25, 2015 11:38 PM
  • Sorry Lindsat-nz, I can see nothing related to"Browser" in the Event log\system when I run ShareEnum. Maybe I need to set some other flag in the event logging system.
    Thursday, November 26, 2015 4:44 PM
  • You are right, Lindsay

    Have the same warnings on all 3 computers in my network and this all among themselves. The machine who is the master browser can run net view without an error and this machine can see all the shares in my network.

    I have a wireshark trace of this behavior, but I can not interpret it exactly because I haven't enough knowledge about the browser protocol.

    Maybe a technician from Microsoft can do it.

    Microsoft must fix it!

     


    • Edited by Dieter-R Thursday, November 26, 2015 7:59 PM
    Thursday, November 26, 2015 7:54 PM
  • Hello I didn't know of this thread but did start one here

    https://social.technet.microsoft.com/Forums/en-US/ff4a5fe2-c826-4282-8709-e925abae444e/loss-of-sharing-of-server-file-connections-upon-upgrade-to-next-win-10-insider-build?forum=win10itpronetworking

    After reading all of the posts in this thread and trying everything. Still the  network shows win 7 machine but not server shares or the other Windows 10 computers. A laptop was up graded to 1115 and same thing .. I worked almost 8 hrs on an upgraded surface pro 3 and had to return to an image of 10532 where all works fine..  BTW the Server can see all the machines. the 1115 machines can ping the server and nslookup returns proper server name and numbers.. This problem has been going on for a while .. As I am a sys admin for several small business I have not upgraded their systems to win 10 for fear of this problem causing disruption of business.. If It does not work on my domain network (server08r2 with all latest updates) how can we trust it to not disrupt business .

    Maybe the Script kiddies at Microsoft should stop trying to make  windows 10 more apple like and pretty and try and fix this issue...

    • Proposed as answer by jfdltd Friday, November 27, 2015 3:10 PM
    • Unproposed as answer by jfdltd Friday, November 27, 2015 3:10 PM
    Friday, November 27, 2015 1:31 PM
  • Just a note to add my "me too!"

    For those of us in a mixed-OS environment, we need old-fashioned networking to (net)work!

    Friday, November 27, 2015 1:46 PM
  • Ok here is what I tried .. on the server I went to dns . and reverse look up zone and made sure all PTR records were correct . due to all the rename unjoin and rejoins there were a lot of caca entries. I cleaned up dhcp records.  on the laptop running 1511 ver I stillcould not see the server or other windows 10 machines.. I then went to server  services.msc and restarted Function Discovery Provider Host and Publication .. I also set them to auto start. I did this on the server and each win 10 installation and low and behold Christmas came early to the laptop running the latest 1511 ver of Windows 10 . I will now try to upgrade the 10532 on the surface to 10586.14 and see what happens.. Ok upgraded to 10586.14 and all domain Computers are reachable . Shared folders on server are accessible.. seems to have worked..  Hope this helps someone.
    • Edited by jfdltd Friday, November 27, 2015 4:51 PM
    • Proposed as answer by jfdltd Friday, November 27, 2015 4:51 PM
    Friday, November 27, 2015 3:17 PM
  • Both these services were already running on the affected Win 10 machine.  Restarting both of them made no difference, it still can't see the CIFS shares on the Two NAS boxes when network browsing but no problem from the named shortcuts.  So I'm afraid that it isn't the answer for me.
    Friday, November 27, 2015 10:33 PM
  • It's really sick you cant access your invisible drives in explorer.

    So I forced it.  Samba works but you just can't see it.

    open up explorer, in this pc you can add network locations.  \\MYNASNAME\directory

    then double click on the shortcut created, add your username and password, then it's added.  Anyway, this sucks.  Was working fine before.


    • Edited by Cresho Saturday, November 28, 2015 3:31 AM
    Saturday, November 28, 2015 1:21 AM
  • also, if you open up explorer, click "this pc on the left, enter \\mynasserverhere    in the address bar

    then you hit enter

    all your directories will appear.


    Im starting to think sambe works, just explorer will not detect it.  You need to do mannual entry even when you mount a network directory as a drive in explorer..

    • Edited by Cresho Saturday, November 28, 2015 3:33 AM
    Saturday, November 28, 2015 3:27 AM
  •   Yes, that was established some time ago. There is nothing wrong with the file sharing. It is the browsing which is stuffed.


    Bill

    Saturday, November 28, 2015 6:13 AM
  • A little more info. Using nbtstat -a ipaddr for each ip on my network, I established that the master browser for the Workgroup in question resides at present on the FreeNas box onthe network.  Since neither of the 'nix boxes can be found by browsing on the "updated" machine, is this because the Master browser is one them?  I have a Win 2008 server on the network which is resolved by a network browse and may try to temporarily force it to be the master browser and see if it makes a difference.

    Saturday, November 28, 2015 3:34 PM
  • OK, I forced the un-updated Win 10 machine to be the master browser. The updatd machine can see this on a network browse but still can't see the two NAS boxes.  :(
    Saturday, November 28, 2015 8:06 PM
  • I have done some more testing and, like others have said, it definitely seems to be a SMB version issue.

    If I turn off SMB 2&3 in the Lanman client I can then see all shared devices, including my NAS WD Mybooklive that was invisible since 10586. I can access the NAS shares also but I can't access the other device shares. I get the dreaded 80070035 error and that means that my Lanman client is asking the Lanman server to display its shares but because the SMB version is different, there is no communication and that results in the client issuing the 80070035 path not found error.

    I have tried various combinations but can't get it working as pre 10586.

    As far as I can see, all my five win 10 10586 comps have got messed up SMB versions hence a failure to communicate the shares. 

    I have left my main comps in the mode where I can see the NAS and hope that MS will fix this soon.

    Edit:- just checked and the master browser is my NAS WD box. No wonder I couldn't find the master on my win 10 comps! If your comp is the master browser all shares are seen but that is because the comp doesn't have to interrogate the master browser thus no communication SMB version problems.

    • Edited by Lindsay-nz Saturday, November 28, 2015 8:24 PM
    Saturday, November 28, 2015 8:17 PM
  • Just to inform: updated Windows 10 to 1511/10586 on 29th and experienced this problem also. All other computers in local network and Windows Home Server shares cannot be found anymore. Windows 10 network troubleshooter indicates 'one or more network protocols are missing' but is not able to fix it.

    I will try some solutions described here and hope this can be fixed.

    EDIT 1-12

    I have a 2nd workstation with the 1511 10586.v14 update which does not have this issue. This is a Windows 10 Home 32 bit PC. The problem still exists on my Windows 10 Pro 64 bit PC.

    • Edited by pwolbert Tuesday, December 01, 2015 6:55 PM
    Monday, November 30, 2015 11:12 AM
  • Edit:- just checked and the master browser is my NAS WD box. No wonder I couldn't find the master on my win 10 comps! If your comp is the master browser all shares are seen but that is because the comp doesn't have to interrogate the master browser thus no communication SMB version problems.

    Not sure that this is true Lindsay.  I got Wireshark to capture packets as I tried to get the affected machine to browse the network.  There are definitely SMB and SMB2 traffic between my machine and the FreeNas box which is hosting the master browser but I don't know enough about the nature of the expected traffic to properly interpret.  There's a fair bit of ipv6 as well which may be complicating things.  I can make the packet captures available for download if someone is competent to interpret them. 

    Tried to add a screen shot of packet headers here but the system wasn't happy.



    • Edited by GeeDoc Monday, November 30, 2015 5:07 PM
    Monday, November 30, 2015 4:53 PM
  • Mmm, but if your master browser is on the NAS box, wouldn't you expect network query traffic to and from it?

    I have just looked again at my setup and got the master browser on my wife's comp and it can now see the NAS box whereas it couldn't before. Doesn't that mean it uses its locally held browser tables rather than having to go out on the network to find the devices?

    Yes, wireshark logs wouldn't be for the faint hearted but interesting you can see both SMB and SMB2 traffic. My comp has SMB2&3 disabled so I guess it means it is communication with the NAS box with SMB1. 

    I dunno, I just know I can't fix this but it is a learning experience trying to figure out what is, and is not, going on!

    Cheers.

    Tuesday, December 01, 2015 9:13 AM

  • Screen shot of wireshark headers from capture, filtered for just the two addresses, 192.168.101.100 is updated Win10 machine, 192.168.101.203 is NAS acting as MBR. Wireshark is on Win10 machine rather than using a replicated port on the switch. The muticast stuff is filtered out but you can see enough I think to see two way communication is going on even though the NAS box does not show up as part of the network.  There's a whole bunch of different protocols in addition to SMB. Interestingly SONOS units are found under the Media devices and they are not Windows.


    Tuesday, December 01, 2015 12:44 PM
  • I just solved it with:

    Go to "Control Panel -> Programs"
    Select "Turn Windows features on or off" (requires admin rights)
    There you will find "SMB 1.0/CIFS File Sharing Support". Enable it!

    Source: https://social.technet.microsoft.com/Forums/en-US/e43bdd35-6dc6-4182-b7a4-1b77cb7fc16a/following-upgrade-to-windows-10-nas-unit-does-not-show-under-network

    Tuesday, December 01, 2015 7:18 PM
  • I just solved it with:

    Go to "Control Panel -> Programs"
    Select "Turn Windows features on or off" (requires admin rights)
    There you will find "SMB 1.0/CIFS File Sharing Support". Enable it!

    Source: https://social.technet.microsoft.com/Forums/en-US/e43bdd35-6dc6-4182-b7a4-1b77cb7fc16a/following-upgrade-to-windows-10-nas-unit-does-not-show-under-network

    Sorry but it doesn't work for me.  This "feature" was already enabled but I disabled it, rebooted, no difference seen. Re-enabled. rebooted, still can't see the non-windows computers.  Some other forum users in the link quoted also reported no difference.  Strange behaviour, one apparent symptom but multiple causes.
    Tuesday, December 01, 2015 8:14 PM
  • Not a solution for me, either. That option is already ticked.

    I disabled SMB2&3 and that allows me to see my NAS and its shares. But it has side effects!!

    Tuesday, December 01, 2015 8:22 PM
  • I disabled SMB2&3 and that allows me to see my NAS and its shares. But it has side effects!!

    I didn't really want to disable SMB2&3 because of the other issues it raises so have a couple of shortcuts on the desktop just of the form \\MACHINE_NAME as a temporary measure until it gets sorted - double click the shortcut and all the shares on the machine are listed in a Window and on the left navigation tree the machine name now appears in the network list - quite bizarre.
    Tuesday, December 01, 2015 10:49 PM
  • Thanks, GeeDoc, I will follow your example.
    Wednesday, December 02, 2015 12:15 AM
  • This does not work for me either.  I can see my windows 7 machines, forcing nas server to use samba 1 doesnt work, but \\mynasnamehere does work trick. or none trick if you think of entering it mannually.
    Wednesday, December 02, 2015 12:45 PM
  • In my case I was able to see all my Windows 10 1511 machines but I didn't see two OpenWrt routers. Although I was able to access Samba shared folders by typing \\routername. I thought that instead of disabling SMB2&3 on Windows machines I'd try to enable SMB3 on Samba servers. And guess what, it works. Now I can see all my Windows machines and OpenWrt routers.

    To enable SMB3 protocol you have to change/set max protocol option to SMB3 in file /etc/samba/smb.conf or in case of OpenWrt /etc/samba/smb.conf.template

    • Proposed as answer by xxxryball Thursday, December 03, 2015 5:36 PM
    Wednesday, December 02, 2015 5:32 PM
  • JazzSutek,

    I tried setting "server max protocol = SMB3" in my smb.conf file, but it didn't help. What are your other settings in the Advanced sharing settings in Windows 10?

    Wednesday, December 02, 2015 9:37 PM
  • I don't know anything about OpenWrt but every Linux installation using Samba4 ( which should be just about everyone by now ) already has "server max protocol" set to SMB3 by default. Adding it to smb.conf won't change anything.
    Thursday, December 03, 2015 1:44 PM
    1.  

      Some further observations.

    2. It's somewhat puzzling that there appears to be one major symptom ie. failure of the Computer Browser function to detect some or all of the other machines on the network and yet various people find some settings that appear to cure their symptom but not other peoples.  One possibility that occurs to me is that Microsoft have slipped in some silent updates and various users are at different release levels.  You can find the exact version you are on by typing 'winver'  at a command prompt. The Win10 machine that has managed to avoid the upgrade says Version 10, Build 10240. The one that is suffering says Version 1511, Build 10586.14.  I'm pretty sure this was originally at Build 10586.04 when it first got hit by the upgrade.  Maybe different builds show different problems as they tinker with the code.  

      Update: It's just had an update to Build 10586.17 but still no complete network browse.
    1. Alhough JazzSutek (and others on different forums) seem to get rid of the issue by setting their Server to use SMB3, I did try this earlier on the Synology NAS and it made no difference.  I don't really think that it's playing a part in the issue. I've been doing a comparison of Wireshark network packets from both affected and unaffected machines on doing a network browse.    There's a lot going on but as part of the negotiations the client issues a SMB Negotiate Packet Request to the Server.  This is saying these are the  dialects that  I understand which of them can you do for me.

      Both machines offer identical dialects, as shown below:

       

      Requested Dialects

          Dialect: PC NETWORK PROGRAM 1.0

          Dialect: LANMAN1.0

          Dialect: Windows for Workgroups 3.1a

          Dialect: LM1.2X002

          Dialect: LANMAN2.1

          Dialect: NT LM 0.12

          Dialect: SMB 2.002                            => SMB v 2.02

          Dialect: SMB 2.???                            => SMB v2 wildcard

       

      Note it isn't offering SMB3

       

      In both cases the SMB server replies with a Negotiate Protocol Response  packet that contains:

      Dialect: 0x0202

      This indicates that it will use SMB 2.02.  SMB3 does not seem to be involved at all.

       

    2. What is obvious is that there are large  differences in the packet exchanges when comparing the two Windows 10 versions with a lot more SMB packets of different types from the machine that is not upgraded and successfully finds all the machines on the network.  It is also obvious that there is little I can do to fix this myself.  Long gone are the days when an OS was simple enough to whip up a quick patch.  Microsoft please extract your digit from where the sun does not shine.  This is not good enough.

    • Edited by GeeDoc Thursday, December 03, 2015 7:21 PM Changed information
    Thursday, December 03, 2015 5:03 PM
  • So I'm the lucky one :-) See http://jazz.tvtom.pl/download/windows1511/network.png Funny thing is that in OpenWrt there is Samba 3.6.25 which do not support SMB3. I don't know how and why it works, but it works (at least in my case). Just to be sure, I switched back temporally to SMB2 and of course routers disappeared from network places.

    There are nothing special about my advanced sharing settings. Here you are 3 screenshots: http://jazz.tvtom.pl/download/windows1511/ (unfortunately in polish)

    Thursday, December 03, 2015 5:33 PM
  • In my case I was able to see all my Windows 10 1511 machines but I didn't see two OpenWrt routers. Although I was able to access Samba shared folders by typing \\routername. I thought that instead of disabling SMB2&3 on Windows machines I'd try to enable SMB3 on Samba servers. And guess what, it works. Now I can see all my Windows machines and OpenWrt routers.

    To enable SMB3 protocol you have to change/set max protocol option to SMB3 in file /etc/samba/smb.conf or in case of OpenWrt /etc/samba/smb.conf.template

    It works for me. I have changed max protocol to SMB3 in my OpenWrt (Gargoyle) router. Now I can see all machines even Raspberry Pi with xbian (didn't change anything in conf file).

    Windows 1511 build 10586.17

    Thursday, December 03, 2015 5:35 PM
  • This is screenshot from Network browse.

    There are a whole bunch of devices that it DOES show including media devices and the internet router but there should be two other devices in the Computer section namely the two NAS which have a load of CIFS shares.



    • Edited by GeeDoc Thursday, December 03, 2015 7:35 PM
    Thursday, December 03, 2015 7:33 PM
  • Perhaps MS should get the Android programmers involved as my phone can see and ping everything!
    Friday, December 04, 2015 12:47 AM
  • My four comps are divided.

    Two see all devices, incl the NAS. They can see the NAS shares but get 80070035 errors on the other comp devices. Net view works OK.

    The other two don't see the NAS but can access the other comp shares. These comps also get the Net view error 1231.

    586 seems to have a split personality on my network!

    Saturday, December 05, 2015 7:57 PM
  • My four comps are divided.

    Two see all devices, incl the NAS. They can see the NAS shares but get 80070035 errors on the other comp devices. Net view works OK.


    What is the upgrade status of the two that can see all devices - Windows 10 or 1511.  If 1511 are they upgrades of the previous OS or clean Windows 10 installs?
    Monday, December 07, 2015 12:44 PM
  • All mine are 1511 fully updated.

    One of the above you asked about was a fresh Insider install and the other upgraded win 7. Not very conclusive!

    BUT, I have just made a serendipitous discovery. Two of my comps have non-admin accounts for the grandkids and from these accounts ALL shares are seen and can be accessed!!

    I have absolutely no idea why this would be so but, hopefully, someone may have some ideas on why this works.

    Also, good for someone else to see whether this works for their non-admin accounts.

    Mmmmmmm!!!

    Tuesday, December 08, 2015 8:11 PM
  • Pretty sure the difference is the local account. Local accounts all good, MS accounts not good.

    Wonder how that affects sharing protocols?

    Tuesday, December 08, 2015 8:56 PM
  • Hi Lindsay,
    I made a new local user without admin rights but it still will not spot the two NAS on a network browse.  My son dropped in at the weekend with a new Dell laptop running 10586.17 which was a clean install and that could not see them either.  The updated machine is running Windows Home but I can't test Windows Pro since my only machine running that is on loan in Germany at present, but I suspect son's machine is running Pro, will ask when I see him.  The machine which has not updated to 1511 and continues to do a complete network browse was updated to Win10 from 8.1.  Am reluctant to force an update on this since it makes a useful comparative system.

    One thing I did note was that immediately post the 1511 update, the affected machine lost it's permanent network address and although it picked up another from DHCP it couldn't see anything else on the network.  Reassigning it's original fixed IP and re-booting brought back it's ability to see other Windows machines on a browse but not itself.  Removing it from the Workgroup and then reassigning to the same Workgroup brought back it's ability to see itself.  Very strange behaviour and I'm very unhappy that I have no choice in postponing these updates 'til I know Microsoft have squashed most of the bugs that inevitably appear.

    Wednesday, December 09, 2015 10:58 AM
  • I feel your pain! Since my last post I have 4 out of 4 seeing and accessing 3 of them but no NAS seen. This no-NAS thing is because I have SMB2 enabled. 

    There is one comp missing under network and it can't even see itself. Really can't fathom what makes this one different as earlier yesterday it was being seen like the others.

    Seriously don't know why I waste more time on this as it is not soluble by we users.

    Cheers.

    Wednesday, December 09, 2015 10:21 PM
  • You have perfectly described the problem. I think some people do not realize that the Master Browser computer acts perfectly normally, and that the other systems on the LAN are unable to retrieve the list from it. All of the shares remain available via NetBIOS names and/or IP Addresses, but they are randomly invisible in the Network folders of the non-Master Browser computers.
    Friday, December 11, 2015 4:44 AM
  • Yes this is exactly the problem. It has nothing to do with Local/MS accounts or Home/Pro version. I can replicate this at will on VMs with any version and any account type. The problem is with network discovery on network folders and can also be seen with nbtstat -r

    C:\WINDOWS\system32>nbtstat -r

        NetBIOS Names Resolution and Registration Statistics
        ----------------------------------------------------

        Resolved By Broadcast     = 5
        Resolved By Name Server   = 0

        Registered By Broadcast   = 4
        Registered By Name Server = 0

        NetBIOS Names Resolved By Broadcast
    ---------------------------------------------
               ?????+++?????+++
               ?????+++?????+++
               ?????+++?????+++
               ?????+++?????+++
                       ?????+++

    See the gibberish on NetBIOS Names Resolved by Broadcast. All computers/shares are accessible perfectly fine via UNC path with their NetBIOS name and/or mapped to drives etc. It's just browsing that is bugged.

    Friday, December 11, 2015 11:57 AM
  • Update to version 10586.29.  Still the same problem.
    Friday, December 11, 2015 10:33 PM
  • Since I'm regarding this problem as "Windows10 1511 cannot get computers list from the master browser with SMB2/3 (and accessing shared resources have no problem)", I added another samba server only for keeping the master browser.
    Aditional settings in smb.conf
     server max protocol = NT1
     preferred master = yes
     os level = 65
    It works for me. (all computers are listed in Explorer, 'net view' command works normally)

    my env.
    LinuxMint(Samba) + UbuntuServer in VirtualBox(Samba for master browser)
    Windows10 1511 10586.29 * 2
    etc.
    • Proposed as answer by kangaroo_flat Saturday, December 12, 2015 2:30 AM
    Saturday, December 12, 2015 12:34 AM
  • Of all the solutions post upthread, only "server max protocol = NT1" in /etc/samba/smb.conf worked for me. I had to add it to two Linux boxes, then a third reappeared on it's own. Win10 10586.29 and Slackware64.

    Cheers.

    Saturday, December 12, 2015 2:35 AM
  • ......
    Aditional settings in smb.conf
     server max protocol = NT1

    ....

    Is this not a retrograde step, going back to an earlier protocol when 1511 should be supporting at least SMB2 as the earlier Windows 10 versions did?  It might be a short term fix but it doesn't encourage Microsoft to fix the problem.

    Edit: Actually on re-reading that sounds a bit dismissive. What I meant was that if it's all working hunky dory with NT1, you won't know if and when Microsoft have fixed it.  Also as a diagnostic,  if NT1 works but SMB2 doesn't, it then suggests that MS have buggered the usage of the SMB2 protocol. At one point I took the NAS that likes to be Master Browser offline which forced my MS 2008 server to be master browser.  Not sure what it's max protocol would be set at but would suspect it might be NT1.  The 1511 machine still did not find the NAS boxes with this as MB.  Will check and see what the 2008's max protocol is.

    Edit 2: The version used in Windows 7 and Windows Server 2008 R2 is SMB 2.1.  Therefore if 1511 is not using the SMB2 protocol correctly it would make sense that it still can't see the NAS boxes even when the 2008 server is the MB.

    • Edited by GeeDoc Saturday, December 12, 2015 7:29 PM
    Saturday, December 12, 2015 12:34 PM
  • Especially since Win10 has no problems accessing a samba server using smb3:

    My Ubuntu server has server max protocol set at the default for Samba4: SMB3

    And Win10 accesses it that way:

    Windows PowerShell
    Copyright (C) 2015 Microsoft Corporation. All rights reserved.

    PS C:\WINDOWS\system32> Get-SmbConnection

    ServerName  ShareName UserName     Credential                         Dialect NumOpens
    ----------  --------- --------     ----------                         ------- --------
    vubuntu1404 public    VWIN10\morbius MicrosoftAccount\XXXXX@YYYYY.com 3.0     1

    What Win10 can't do is "discover" my Ubuntu server under Network in explorer. It has no issue accessing it.



    • Edited by Morbius1 Saturday, December 12, 2015 8:18 PM
    Saturday, December 12, 2015 8:14 PM
  • hello
    Sunday, December 13, 2015 12:59 AM
  • I have 6 computers upgraded to Windows 10 Pro. Before they were Win7 and Win8.1. There is also a Netgear NAS RN-104 data bank in the network.  It was no any problems with network computer visibility before including the NAS device. The problems started with 1511 build 10586 upgrade of Windows 10. Not all computers were seen in the network, some of even didn’t see itself. The NAS device couldn’t be seen  at all (not listed in the network explorer) although it could be accessed by its name (backslash\NAS). I have been looking for the possible solutions.

    The interesting thing is that when I haved stopped and disabled HomeGroupProvider  service on the two computers (on the others it had to be running)  all network computers appeared to be listed in the network explorer but still not the NAS device.

    HomeGroupProvider service is related to previously created (but never used) Homegroups. At first I have disabled HomeGroupProvider service on all computers and then started to enable it back one by one, checking if computers appear in the network.

    In the same moment the command prompt command of net view /all gave the  System error 1231 saying that The network location cannot be reached.

    Lastly I’ve managed to see also the Netgear NAS device on the all computers in the network explorer.

    In my network it so happened that the NAS device was the Master Browser computer and was configured for SMB version 3. I think that the problems with visibility of network devices are working bad if the Master Browser computer has SMB 3.

    When I  have changed the version of SMB to 1 on that NAS all computers and NAS device  started to be seen in network  explorer as it used to be before with Win7, Win8.1 computers although the SMB was on level  3 as well.

    And the net view /all command started to work perfectly.

    I hope my research will help some of you also but the real reasons are the Microsoft unknown changes in the 1511 Win10 update.


    • Edited by JacekCh Sunday, December 13, 2015 9:00 PM
    Sunday, December 13, 2015 1:01 AM
  • Nope!  does not work for me.  Tried everything.  It sometimes works, and it doesn't work sometimes.

    Same thing with remote desktop through pptp.

    Sunday, December 13, 2015 7:36 PM
  • I have this issue, able to connect via \\(NETBIOSNAME), but totally unable to detect anything but other windows 10 computers. Can't detect my phone, my TV, my NAS. As mentioned, net view /all gives a system error. 

    Diagnostics of netbios itself are fine, which would be expect since you can use the names. Samba is fine. Android is able to detect and connect just fine. 

    I had postponed windows updates because I was out of the country.  Apparently I should have postponed them indefinitely. This is driving me nuts. None of the listed fixes here or elsewhere have done anything, which isn't surprising, as this increasingly sounds like a glitch in Windows itself.

    Monday, December 14, 2015 5:19 AM

  • I will update this thread again once I have some more information.

    Hi Adam,

    Any news? This really is the worst bug I have come across in quite a few MS releases....

    Tuesday, December 15, 2015 12:05 AM
  • Thanks

    Working on these setting for now - Only had to update one server and then all the others

    showed up the minute I put this on one of them.

     

    Wednesday, December 16, 2015 12:44 PM
  • I've been working on designing a NAS storage appliance for my company. I've been testing like mad the last 6 months. What I can say with certainty is that windows sharing is probably the most inferior sharing arrangement of any operating, and it really has always been this way. NFS isn't even an option, only SMB. furthermore, the network locations folder (or whatever it is, virtual folder?) is inconsistent and unreliable. What I've traditionally found is that if you can get the share to show up in the network virtual folder, you should be good to go as far as the OS is concerned... if you can't get it to show up there, you'll likely have problems trying to mount or access another way... like with the address or domain in the search bar.

    It is so incredibly easy to access a share from linux and Mac and always has been, but windows has always had serious issues in that regard.

    The recent update did appear to have broken things even further. This entire area of windows has needed a redesign since the late 90s... but instead Microsoft decides to focus on graphics, and overly complicated and un-traditional interfaces.

    I was able to access the my shares using //HOSTNAME in the search bar, it popped up completely randomly 5 minutes after I ran that command. So at the moment I can see the share, but can't access any folders within it. As usual, I now need to spend hours getting windows to act normally with shares, I just hope the update hasn't broken sharing even more.

    Everything was working adequately... then I updated; nothing else was changed.

    It also appears that the update has reverted a great number of settings. I had configured my system not to install updates automatically, but MS changed that back... do they seriously not understand how critical and dangerous their updates, just like everyone else's, can be? I mean, my god... these guys assume every windows 10 box is being used for gaming and movies... we'll, I guess if that's the way they want it... I'll just have to stop using them for everything technical or important. MS has seriously lost their way in the search for control and profit.

    Wow this is unbelievable: http://www.windowscentral.com/windows-10-november-update-issues-bugs

    After reading this, it all appears to be true. The update did remove a lot of my programs (e.g. CPU-Z), installed apps previously removed, reverted a lot of my default apps back to crapy MS equivalents. It removed a lot of software from competitors.

    I guess its official, Microsoft can't be trusted with something as critical as an operating system anymore...

    • Edited by gunslingor1 Wednesday, December 16, 2015 3:17 PM
    Wednesday, December 16, 2015 2:57 PM
  • The bug remains also on build 11082.1000. Very, very sad. How can a company be so ignorant. Has anyone heard a statement from Microsoft? If I reboot my Linux server all shares can be seen by 1511. But after a while all Linux shares are gone again. Very, very frustrating. Microsoft should listen to their users.
    Friday, December 18, 2015 7:26 AM
  • Are there any news? The new insider build 11082.1000 also contains the annoying bug. I would like to see some progress...
    Friday, December 18, 2015 7:31 AM
  • Standard 1511 is now at Build 10586.36 - problem is still there. Perhaps not surprising since Insider builds also have the issue.  Was recently told that SMB & CIFS are not published open standards and that Microsoft are under no obligation not to make changes.  SMB and CIFS on non-windows platforms are reverse engineered.
    Friday, December 18, 2015 3:18 PM
  • Open standards or not, I can't access my Windows shares from Windows 10 as of the last update (FWIW, I can access them just fine from my Macs). I don't think this is limited to non-Windows platforms.
    Friday, December 18, 2015 8:00 PM
  • If I reboot my Linux server all shares can be seen by 1511. But after a while all Linux shares are gone again. Very, very frustrating. Microsoft should listen to their users.
    While there is no other solution, write in Linux Samba server conf file "max protocol  NT1" and everything works again.
    Saturday, December 19, 2015 7:00 AM
  • I can connect but the shares aren't shown in the Explorer. This is the case at least since build 10565 but I think also before that insider update. I wonder why nobody has seen this before. Everyone who uses a NAS or Linux server should remark this. If I put the path directly into the Explorer (e.G. \\nuc\data) it works also with 1511 alias build 10586. It isn't shown as share on the right side of Networks but on the left side (folders). This behavior is very strange to me and makes no sense. I think this a bug. Shame on you Microsoft. How can such thing happen?

    Is everyone having the same issue as me?  All Win 10 (1511) PCs, the first to boot, finds all inc SMB/CIFS etc. but the others only see (in file explorer) Win PCs. If I turn off the "master", one of the others will now see all and son on and so forth.

    Is there some kind of master PC forwarding the network info to others in Win 10?

        
    Saturday, December 19, 2015 1:43 PM
  • Is everyone having the same issue as me?  All Win 10 (1511) PCs, the first to boot, finds all inc SMB/CIFS etc. but the others only see (in file explorer) Win PCs. If I turn off the "master", one of the others will now see all and son on and so forth.

    Is there some kind of master PC forwarding the network info to others in Win 10?

    I suspect that this depends on which machine is the so called 'master browser' on the network.

    The master browser maintains a list of all the machines in the network and other machines on the network ask the master browser for this list when they do a network browse. The  issue here seems to be that a Win 1511 machine doesn't query the master browser correctly to get a complete list, it's missing devices such as linux based NAS.  However if a 1511 machine happens to be the master browser and it does a network browse it will see the NAS having got the ALL the info when it assembled it's master list of devices in its role as master browser. This link gives a bit more information on the master browser and how to find it if you are interested.

     

    http://scottiestech.info/2009/02/14/how-to-determine-the-master-browser-in-a-windows-workgroup/

     

     


    Saturday, December 19, 2015 3:59 PM
  • Many thanks, most informative and now I don't feel alone. Did many searches and nothing came close to that explanation, which seems to be my exact problem.
    Saturday, December 19, 2015 8:42 PM
  • The Windows computer browser service actually goes back to Windows NT. It will eventually have to go because it depends on Netbios over TCP/IP, which is not supported in IPv6. (Originally is ran on Netbuei then Netbios before Windows adopted TCP/IP in 2000).

      I guess the young guns working on Windows 10 never use it and have no idea how it works. I hope there are a few old hands still working there who can get it back on track.


    Bill

    Saturday, December 19, 2015 11:46 PM
  • No, that's not true. Some Microsoft developers are contributing to Samba since 2011.
    Tuesday, December 22, 2015 9:41 PM
  • Same here. After windows update none of our PCs at home can see our NAS. Which is basically the worst case scenario, since all our work is on it.
    Wednesday, December 23, 2015 8:25 PM
  • Great info here, and it all matches my situation, so why oh why is MS impervious to our plight? 

    Just beggars belief that they can pretend nothing is wrong.

    Quite frankly, it has reduced my respect for MS and this product after being a loyal Insider since Oct 2014.

    Tuesday, December 29, 2015 8:33 AM
  • I signed up to provide an insight into my experience to try to fix this.  The two things I have done which appeared to be successful in my case to resolve this is

    1. As administrator and from command line, run the following to disable SMB2 (and 3) and enable SMB1

    sc.exe config lanmanworkstation depend= bowser/mrxsmb10/nsi
    sc.exe config mrxsmb20 start= disabled

    2. Doing the above may not necessary sort out the issue and I then had to turn on sharing.  From Control Panel\Network and Internet\Network and Sharing Center\Advanced sharing settings, expand the "All Networks" section and select "Turn on sharing so anyone with network access can read and write files in public folders"

    Because I was mucking around with it so much and I changed so many things, I then had to troubleshoot to check some services were running.  Specifically I ensures that Computer Browser, Function Discovery Provider Host, Function Discovery Resource Publication, Server and Workstation services was running using services.msc.

    My Computer Browser services was not running and I also had to troubleshoot that. It turned out I corrupted my HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanWorkstation\DependOnService.  I reset the parameter to "bowser mrxsmb10 nsi" (I think I had to delete "mrxsmb20".  Rebooted and I could see all the shares from Windows 10 build 1511 machine. 

    Have tried on two Windows 10 64bit pro build 1511 machine and after multiple reboots, everything seems stable.  

    Hope this helps someone


    Thursday, December 31, 2015 8:58 AM
  • But, can you see both win 10 shares AND Linux based NAS servers? That is where we are having the problems.
    Saturday, January 02, 2016 8:50 AM
  • I have a Windows 7 Pro, 64 bit machine as well as a Ubuntu server (running Samba 4.1.6) on my network.  Both machines are seen consistently.  The Master Browser list has also rotated between my Ubuntu server, Win 7 and also Win 10 (build 1511) machines.  And the machines are visible in the network. 

    I don't know how else it can be tested.

    When I ran just the sc.exe command, the computers are only visible to the Windows 10 computer with the Master Browser list.  Setting the public shares for all networks seem to make it all visible to the Windows 10 computer



    • Edited by sirzur Saturday, January 02, 2016 11:16 PM
    Saturday, January 02, 2016 11:06 PM
  • But what you have done is forced your Win10 PC to use SMB1 protocol. You are missing out on performance and functionality benefits of higher levels of SMB. See here for Microsoft's way of enabling/disabling SMB2/3 (should look familiar to you). Also there are links on that page as to the benefits of SMB2/3 usage.

    How to enable and disable SMBv1, SMBv2, and SMBv3...

    Note also the warning in bold at the top of the article: 

    Warning: We do not recommend that you disable SMBv2 or SMBv3. Disable SMBv2 or SMBv3 only as a temporary troubleshooting measure. Do not leave SMBv2 or SMBv3 disabled.

    Personally, what I have done is left SMB2/3 running as my Linux server is running samba-4.1.6 and is SMB3 capable (and the Win10 machine talks to the server via SMB3, it just can't browse it). I have then pinned my server as a quick access link. I'm finding this quicker than browsing via the network - although I only have a single Linux server on the network. But that isn't the fix....

    Tuesday, January 05, 2016 8:20 AM
  • I agree its not a solution! Specifically because my setup basically requires the ability to browse as I have public media shares I wish to be used by whoever may be connected as a guest at my house. It is currently only function because my Linux box is force using SMB1 and I don't like to do things that way (as I'm sure by all the posts available on the topic no one else does. My non-useful post here was so I can at least follow the thread for updates. Has Microsoft acknowledged this real problem?
    Tuesday, January 05, 2016 3:05 PM
  • I solved it by not letting my linux sambaserver to be the master browser. I disabled it. And i put my router in samba mode so it would become the master browser. Now all my machines show up in the networkfolder.
    Tuesday, January 05, 2016 9:08 PM
  • I had same problem. Neither Windows 10 computer nor Ubuntu computer could access each other's files, as they did with Windows 7 before upgrade. Fixed half the problem by opening Windows File Explorer and typing "\\linux.local" in address bar. It created a Quick Access that allows me to read the Linux files. Unfortunately, still can't read the Windows files from the Linux computer. It either asks for a Workgroup password, which I don't have, or it tells me it can't open the User folder, which is visible. My Windows folders are set for sharing with "everyone." 
    Friday, January 08, 2016 3:11 PM
  • Hi All,

    I wanted to provide an update on this thread to let you know that we are currently investigating this issue and I am working with the product group to determine root cause. The issue we are investigating is in regards to 'Network Discovery' not locating devices on the network.

    The issue appears that Windows 10 is not broadcasting out an NetBT or RAP requests when searching for the devices on the network and only uses WSD protocol. If you navigate to Explorer > Network and changed to Details view and then add 'Discovery Method' to the column bar you should see that if you are discovering any devices they are more than likely only being found via WSD.

    If you are encountering an actual issue accessing a network share (such as inputting \\location\share) that is more than likely a different environment issue. If you are encountering this type of issue, feel free to capture a network trace when reproducing the behavior and sending me the trace data to arudell at Microsoft dot com and I can take a look at let you know what might be preventing connection from being established.

    Regards,


    Adam Rudell | Windows Networking Beta | Microsoft Corporation

    Monday, January 11, 2016 3:58 PM
  • If you are encountering an actual issue accessing a network share (such as inputting \\location\share) that is more than likely a different environment issue. If you are encountering this type of issue, feel free to capture a network trace when reproducing the behavior

    @ Adam

    I have noticed NSI mentioned in this and related threads.  In one example, a blogger is suggesting that there is a permissions problem associated with it.  Are you aware of this?  I only just realized today that there could be a relationship between the two because of this fact.  In this thread it apparently has something to do with service dependencies.  In the other it is a repair procedure being thwarted by bogus messages.

    Also, I am getting the suggestion to enable LMHOSTS even though I don't use them?  Would it help to make some?

    Note that my primary networking problems with W10 were solved by reconfiguring to make sure that Local IPv6 was supported.  So, by now being able to use a Homegroup reliably I no longer see Workgroup problems in the GUI though there are still quirks to be seen on the command line side (e.g. using net view,  nbtstat etc. as shown in this thread.)  



    Robert Aldwinckle
    ---

    Monday, January 11, 2016 10:10 PM
  • Thanks for the update Adam.  Hitting a client of mine with purely Win10 v1511 machines - purely about discovery. Can connect via UNC OK.

    Trevor

    Tuesday, January 12, 2016 5:21 AM
  • purely about discovery.

    Seen where?  In the GUI or in the command line?  FWIW using Adam's tip about the Details view in Networks in my Hyper-V host (which I have prevented from becoming the Master Browser because it is multi-homed), I can see the other hosts were found by WSD or NetBIOS.  Meanwhile the only host which (sometimes) gets a clue about all the others according to nbtstat is Surface RT 8.2 (which of course is not W10 or a server).


    Robert Aldwinckle
    ---

    Tuesday, January 12, 2016 5:44 PM
  • From MS today:

    'Bug<u1:p></u1:p>: Win10 client cannot access a share on a master browser from “Network” icon.'

    'There is a hotfix being tested for this, and at present they are targeting March for a public fix.' <u1:p></u1:p>

    Tuesday, January 12, 2016 7:19 PM
  • I don't remember where I found this since I began looking everywhere 2 weeks ago but I want the credit
    to go the the gentleman as listed below and want to thank him enororously for this fix.

    mikele

    Junior Member
    Join Date : Nov 2015
    Posts : 16
    w10 x64 N


    I found a way...

    Apparently the problem comes from build 1511 because it uses samba 3, so you have to disabled it like       this:     

        Do a search for CMD using the search Magnifying Glass icon near the Start menu.

        It will appear at the top of the search window. Right click on it and run as Administrator.

        Type these two lines together like this next to the blinking cursor in that black Command Prompt box.
        (You can just highlight and copy them from here and paste them next to that blinking cursor.

        sc.exe config lanmanworkstation depend= bowser/mrxsmb10/nsi
        sc.exe config mrxsmb20 start= disabled

        If you copy and paste them from here as text they will run immediately in the CMD Prompt after being
        pasted next to the blinking cursor.

        Now Reboot. This MUST be done on each and every Windows 10 that was upgraded to build 1511.

        This disables Samba 3.1.1 which is the problem that caused this whole situation.
       

        Of course MS updated to this version of Samba obviously without knowing it was going to kill off
        our Local Network sharing between computers.

    This worked for me, I can see all my mapped PC's now, windows XP, windows 10 and Threshold 2 and all files and folders are now back to being able to be shared on all PC's

        more infos : Synology Forum View topic - Windows 10 Version 1511 and SMB3

        
    Thursday, January 14, 2016 2:10 AM
  • Thank you, mikele and HAndreasaen! This is the first solution that actually worked for me. I had lost the ability to browse or access my WHS file shares by name with the Windows 10 update, but this has restored the lost functionality.

    Here's the post on the Synology forums: https://forum.synology.com/enu/viewtopic.php?f=49&t=106924

    Thursday, January 14, 2016 7:15 AM
  • The workaround consisting in disabling SMB2/3 did well in a fisrt time... However it was due to the euphoria of having finally found a way to access my company NAS through Windows 10. SMB1 protocol is obsiouvly out-dated and subject to instability as several of my coworkers can't simply copy a single file to our NAS without failure.

    According to Michael S McElrath, an hotfix would be currently tested. Could we've got a link to that announcement please ?

    I'll look forward for a solution but in a professional context, such a persistent problem (3 months) lead us to seriously question our network choices.

    Thursday, January 14, 2016 10:18 AM
  • My inquiry on this issue was sticky backchannel to Microsoft, no official announcements yet. I was concerned that no one had even acknowledged that the problem existed despite the hundreds of posts on this subject.

    I’m surprised that it will take 5 months for this problem to be fixed (I reported the problem the first week of November). For my company this is a deal breaker so we are running Windows 8.1 with Classic Shell.

     
    Thursday, January 14, 2016 5:14 PM
  • What finally worked for me was the installation of Windows 10 Build 11099.rs1_release.160109-1156 which was released just a couple of days ago. Looks like Microsoft is already experimenting with those remedies which were going to be officially released no sooner than March 2016.

    My Linux NAS units are visible on the network again after having not seen them for several months!

    Just put yourself on the fast line with Windows updates...

    anhil

     
    Thursday, January 14, 2016 5:59 PM
  • What finally worked for me was the installation of Windows 10 Build 11099.rs1_release.160109-1156

    Even with it Details (e.g. as mentioned by Adam) still look patchy.

    http://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_web/networked-computers-description/744767da-420b-4fc9-8778-bc59d1eb824e?msgId=bd2fc0b2-b891-4908-ae02-4c6cf471ca4a

    Also, why won't File Explorer remember my Details preferences?  I have to keep checking them every time I want to see them.



    Robert Aldwinckle
    ---

    Thursday, January 14, 2016 6:14 PM
  • So let me get this straight. Microsoft is saying that it is going to take 5-6 months to roll back the change that broke file sharing? Literally making all windows boxes unusable on a public (guest access) LAN for half a year? Is that correct?

    Does this not sound ridiculous and unacceptable to anyone else? Firstly, why the hell can't we just rollback the fucking update that did this in the first place? Oh right, Microsoft insists on not allowing user control of updates... "You will take our updates and like it! Even if we break your shit and cost you millions of dollars...we at Microsoft do not believe in best practice accepted throughout the IT industry, we know what is best for 100 million computers distributed throughout the world and configured entirely differently. Yes, we at Microsoft know what is best... we broke file sharing intentionally to protect you from viruses."

    I think they don't give a rats ass about how their operating system is perceived anymore, this is complete incompetence for any software development company. They are going to lose so much market share over this stupid forced patch management philosophy... I mean seriously guys, do you realize most nuclear plants are, in part, being run using custom configured windows boxes... does MS really think it's smart to go updating these willy nilly? It is so stupid, they are giving up the bulk of their market share to get a fraction of a percent of the lowest common denominator market share. What was once a operating system that was flexible and useful for infinite applications is now dead, no better than a gameboy... pretty much single use application. I wouldn't use windows for anything technical or critical at this point, I don't recommend them for business use either. That goes for windows 8 and 7 as well... they just can't be trusted anymore.

    I can't believe how far this company has fallen, and it baffles me why they are allowing this impending nose dive. It's clear they have lost their way, the philosophy that pushed me in the direction of windows instead of Linux or Mac the last 20 years is completely gone from Microsoft.

    They've turned a great OS into a monster. They've obviously completely destroyed their entire patch management infrastructure in the rebuilding process too, because this exact bug has happened before many years ago in windows 7 or XP (I forgot which). Trust me, this isn't the first time MS has broken network sharing with a patch... it is also not the first time MS has broken something on windows 10 with a patch they forced down our throats. And yet, they continue to claim they know what is best for all windows computers regardless of application... MS can go to hell.

    Thursday, January 14, 2016 7:39 PM
  • same issue with latest insider 11099
    Friday, January 15, 2016 8:26 AM
  • same issue with latest insider 11099

    I think it would help to be more specific about your symptoms.  E.g. the subject implies it is about "connecting" but seems to have desolved to automatic discovery but even that may be working now for me in File Explorer provided I use the Refresh button after ensuring that I should be connected, e.g. after powering a machine on.  So, is having to press Refresh part of the "same issue"?  Maybe we just aren't waiting long enough?  E.g. somewhere I read that it could take up to 48 minutes for a Master Browser to get a full list.  I must admit that I have not tried being that patient.   ; )


    Robert Aldwinckle
    ---

    Friday, January 15, 2016 4:37 PM
  • I know what the problem is. Windows sharing is terrible, it always has been terrible and is literally so terrible that it's un-maintainable. Windows has always been sub par to Linux and Mac on this, going all the way back to the days of the hair bands.

    They rebuilt the network interface once from the ground up (windows NT I think), but it was a rebuild intended to provide the same interface and functionality (which is the root cause of their difficulties); it was pretty useless before this. Anyway, that one rebuild made it sufficient for a while, about 10 years. This is the first time since I've seen them utterly break it since.

    But honestly, I've been asking for a ground up rebuild of windows sharing for a long time. How about adding support for NFS? How about better controls for discovery. How about manually restricting the sharing protocols or IPs needing to be pinged. How about better integration of the Network and Map drive interfaces, they can compliment each other; instead they overlap and cause confusion. How about dealing better with multiple network locations all requiring different guest and user names. Just a few of the imporvements that have been needed since the 80s... it pisses me off they choose much less important things to focus on since the beginning, like an office ribbon, or redesigning a start menu a thousand times.

    I've been also looking for something, anything, that can take the burden off of Microsoft for dealing with sharing; some third party application. But, I have found nothing but a few hacking tools, which aren't really an appropriate solution for general sharing.


    The worst part of all this... MS is trying to take control and dumb down the OS. In previous versions of windows you were able to adjust desktop icon spacing, now the only way is via the registry. This is just one of 10,000 things MS took away from us in windows 10... it's great philosophy for 90 year old grandmothers, but not the rest of us.
    • Edited by gunslingor1 Saturday, January 16, 2016 9:45 PM
    Saturday, January 16, 2016 9:39 PM
  • Just to report that Windows 10 1151/10586 got up to something like .70  (was originally reported at about .4) on 2 machines that I upgraded over the weekend.

    Both had this problem, I have reverted both to Win7. I can't actually use the new Win10 until this is sorted out, and find the duration November (broke it) -> March for a fix to be unacceptable. I would have thought that this would be a case of dropping everything, ESPECIALLY as Win 10 upgrade is now a default - there will be lots of users picking up this update by accident who will then be pretty annoyed at the broken networking.

    Please Mr Microsoft - an urgent fix.

    Monday, January 18, 2016 1:31 AM
  • Agree, Nov to Mar to fix is mind numbing.

    Maybe even worse, is the silence surrounding this issue.

    Monday, January 18, 2016 10:41 PM
  • Ok, I can now confirm, that the lates insider build 11099 indeed solves this issue. I have tested that with two virtual Windows 10 installations at home.  At work it seems  to be another problem which also occurs on Windows 7.
    Wednesday, January 20, 2016 8:16 AM
  • Thanks for the update, jarau. I don't have a NAS installed at present so can't test that. 

    Wednesday, January 20, 2016 8:42 PM
  • I've installed the Insider Preview build 11099.1000, and unfortunately the problem is still present. What was your version jarau ?

    My company NAS is once again only reachable when SMBv2/v3 is disabled... Which is not usable as uploading data through SMBv1 appears to be very unstable on my co-workers computers !

    Thursday, January 21, 2016 8:49 AM
  • I'm also using the 11099.1000 (desktop shows 11099.rs1_release.160109-1156). At work I've used the wrong work group. After correcting that the network shows me all shares almost instantly. Also at home my NAS, NUC and Panasonic TV are now browsable again.
    Thursday, January 21, 2016 9:45 AM
  • 11099 shows a Linux workstation for me under Network, cannot see it on 10586. So improvements in 11099 I would say.
    Thursday, January 21, 2016 9:40 PM
  • Insider build 11102 also shows the Samba shares:-)

    It seems, they are on the right way.

    Friday, January 22, 2016 8:53 AM
  • I totally sympathize with you gunslinger, and also agree with your frustration and anger, as I too, a lowly home user with 3 laptops, 4 desktops, a NAS and apple ipads, have been working on this for bloody ages, 2 months, soooo many wasted hours, so many interruptions to users working having to stop save and reboot, so exhausting.

    At first I thought it was just me and the way I had things set up, but as with most things, its not until you start digging deeper (This thread, among many many others), you FINALLY realise your not the ONLY one!

    I have worked through all the published reported fixes. only ONE worked, and that was VERY temporary, and NO LONGER works! That was this:

    1/ Run cmd as admin
    2/ sc.exe config lanmanworkstation depend= bowser/mrxsmb10/nsi
    3/ sc.exe config mrxsmb20 start= disabled
    Restart and done! You will see all your NAS in your network.(Only worked for a couple of days for me for some reason).

    Luckily I have read through this thread and now know I need to wait for MS to fix it in the coming months, damn embarrassing for MS, who is getting their respective asses kicked for this, and the silence...oh the silence, it is deafening from MS, almost as bad as the latest Clash of Clans ridiculous update, what is up with these big companies that could give a crap to the very people that get them to where they are!!!

    Anyway, if this helps anyone, that's cool, mainly for the home users, you IT dudes using NAS at work have done other patch-ups.

    This is not new, I'm just writing as I did it to make it easier for home users hopefully.

    Clik on "Network", type \\diskstation hit enter and depending on your shares setup, you should see the list of shares published.

    Right clik on the diskstation name in the title bar, and drag it to the desktop as a shortcut.

    Apart from mapping all the drives you need, this is a workaround, until MS get their shit together.

    Well it works for me, on ver:10.0.10586

    Cheers

    Friday, January 22, 2016 2:34 PM
  • It would seem the reason that 11099 and 11102 now work is that these versions use NetBIOS for discovery as opposed to WSD in 1511 builds. The great leap back to the future!!

    My two 1511 comps can only see each other and not the Linux based networked printer, or the two insider builds, but both 11099 and 11102 comps see everything, incl the Printer.

    But the big question has to be asked - how did this fiasco get out in the wild? Perhaps the reason MS are saying nothing is that they are too embarrassed? Fancy not listing a fixed network discovery in the change list for 11099.

    And if MS think we are too critical and/or ignorant, whose fault is that?

    Now get the 1511 builds patched or upgraded.

    Saturday, January 23, 2016 3:46 AM
  • It would seem the reason that 11099 and 11102 now work is that these versions use NetBIOS for discovery as opposed to WSD in 1511 builds. The great leap back to the future!!

    That is what needed to happen to work with earlier versions of Windows (and CIFS shares). Adam said in his update on January 11 that using WSD only was the basic problem with version 1511.

      The fix in build in 11102 looks promising. That machine seems to behave normally with my Win 7, 8.1 and XP shares. Of course my 1511 Win 10 machines still don't work properly because they still use WSD only and don't get the browse list from the master browser (which is a non-Win 10 machine because I have stopped the computer browser service on all of the Wiin 10 version 1511 machines).

     


    Bill

    Sunday, January 24, 2016 5:13 AM
  • have stopped the computer browser service on all of the Wiin 10 version 1511 machines).

    I didn't go that far.  Only stopped the browser on my Hyper-V host (because it is double homed).  It is still 10586.063 but, as I mentioned, can see in File Explorer Network everything that is running, at least after a Refresh.  The other factor that I'm not sure about for its significance is that they are all in the same Homegroup. I suspect there must be some connectivity effect from having that, if only as a list of possible hosts.



    Robert Aldwinckle
    ---

    Sunday, January 24, 2016 9:05 AM
  • have stopped the computer browser service on all of the Wiin 10 version 1511 machines).

    I didn't go that far.  Only stopped the browser on my Hyper-V host (because it is double homed).  It is still 10586.063 but, as I mentioned, can see in File Explorer Network everything that is running, at least after a Refresh.  The other factor that I'm not sure about for its significance is that they are all in the same Homegroup. I suspect there must be some connectivity effect from having that, if only as a list of possible hosts.



    Robert Aldwinckle
    ---


      I can't see how homegroup membership would affect NT-style browsing, but one never knows.

    Bill

    Sunday, January 24, 2016 11:56 PM
  • And just to make things interesting.....now it is showing again in "My Network" I can't work this out it's almost the old....do do do do Xfiles! I must profoundly state that I did NOTHING, Diskstation is now visible on my LAN...wtf Microsoft?

    • Edited by stikxx Monday, January 25, 2016 12:57 PM
    Monday, January 25, 2016 12:56 PM
  • now it is showing again in "My Network" I can't work this out


    How long are you waiting?  Supposedly a Master Browser should be given 48 minutes to get its list.  My Tablets could not wait that long.  With nothing else running they would be asleep or hibernated if it had to take that long.



    Robert Aldwinckle
    ---

    Monday, January 25, 2016 4:57 PM
  • I wanted to let you know that we were able to identify the issue and ultimately find out that a fix was already in the works and checked into our latest builds. I tested on build 11103 in my environment and confirmed that the machine is able to find other devices on the networking using both NetBIOS and WSD when performing Network Discovery.

    I see that 11102 is available for WIP so it should be contained within that build image as well.

    Please do some testing and let me know the results.

    Thanks!


    Adam Rudell | Windows Networking Beta | Microsoft Corporation


    Monday, January 25, 2016 5:40 PM
  • Hi Arudell,

    Thanks for the update. Any idea when this fix will be rolled out? I hope we don't have to wait for the "Redstone" update


    Monday, January 25, 2016 11:57 PM
  • Thanks for the info, Adam.

    My two 11102 builds see and accesses all windows shares, as well as my networked printer (would be a Linux derivative I presume). So, success!

    The discovery method starts by showing NetBIOS for all, then changes to WSD for the 1511 comp and itself (11102). The printer and another 11102 comp stay as NetBIOS.

    After checking, it looks like a 11102 comp shows WSD if it is the master browser, otherwise it shows NetBIOS.

    I'd be happy to see these changes applied to the 1511 builds asap!

    Tuesday, January 26, 2016 12:25 AM
  •   Because this thread has got so long I propose to open a new thread to discuss the fix for this problem which is available for testing in build 11102.

      I will call it Testing of the fix in build 11102 for CIFS/Samba sharing problem.


    Bill

    Tuesday, January 26, 2016 5:56 AM
  • I am in discussions with the PG right now to understand a possible ETA on when fix will be available. I'll keep you posted.


    Adam Rudell | Windows Networking Beta | Microsoft Corporation

    Tuesday, January 26, 2016 4:05 PM