Even at the latest update of windows 10(pro, home 64 or 32bits) i think is 10586.28, the machine does not see other shares like a Qnap nas, ws2012r2std and two hyper-v machines inside the server. It only works if it is the Master Browser. There is a workaround disabling smb 2 and smb3 but that is retrograde isn't it ?
i think this is the same problem like here: http : //answers.microsoft.com/en-us/windows/forum/windows_10-networking/win10-10586-found-fix-for-system-error-1231-bug/5ca0164e-33d4-46bf-9ac3-3751499f2430?page=1
I remember when installing TP's of windows 10 on VM's it would not see older OS's shares. The fix for me was just to reshare them on those machines and then they popped up. All caps maybe a bit drastic and hard on the eyes but maybe also has something in common with case sensitive shares? Regards
SMB seems to have gotten broken with 1511. Try this temporary fix until MS fixes the problem. To disable SMBv2 and SMBv3 on the SMB client, run the following commands: sc.exe config lanmanworkstation depend= bowser/mrxsmb10/nsi sc.exe config mrxsmb20 start= disabled Reboot and you should be fine. Reference: I can't post a link yet but search for "kb 2696547" How to enable or disable SMB protocols on the SMB client
Thanks guys for the help. I verified computer browser service up and when i disabled the smb2 and 3 protocols it does see the shares, but only in the master browser machine. Will see if today's update rollup gives something new...
same crap with update 10586.36. in my next-to-last attempt I made the qnap nas the master browser, shut down all computers, then started all up one by one, every pc were showing BUT the win10 laptop, then the win10 virtual inside an already seen ws2012r2. Summary: the two win10 machines only see themselves, and win7 pc. all other machines can see and access shares on the two win10 machines.
PROBLEM SOLVED !!! Erased the tablet and installed windows 8.1 factory image. Now That's a fast tablet !!! Everything works as it should.