

- #WD MY CLOUD BROWSE IN EXPLORER UPDATE#
- #WD MY CLOUD BROWSE IN EXPLORER UPGRADE#
- #WD MY CLOUD BROWSE IN EXPLORER WINDOWS 10#
- #WD MY CLOUD BROWSE IN EXPLORER PC#
- #WD MY CLOUD BROWSE IN EXPLORER BLUETOOTH#
then click the button labeled, "Properties".
#WD MY CLOUD BROWSE IN EXPLORER BLUETOOTH#
a Bluetooth Network Connection, an Ethernet adapter and a Wi-Fi adapter.
#WD MY CLOUD BROWSE IN EXPLORER WINDOWS 10#
Recently, the laptop with Windows 10 was not seeing the NAS in the network when usingĮxplorer. My desktop is using Windows 7 and my laptop Windows 10. I have a Synology NAS and it has been working fine. I too have recently been having this problem.

If you know of any great tools for browsing Workgroups that don't rely on the older protocols I'd be happy to hear from you. I re-iterate that this is just a short term workaround, Computer Browsing for workgroups is history for Windows 10. You may even find that a non Microsoft third party device on the network attempts to take over the Master Browser role. MaintainServerList from Auto to No on all other PCs in the Workgroup.
#WD MY CLOUD BROWSE IN EXPLORER PC#
If you want to be absolutely positive no other PC takes the Master Browser role you can set the value of If it is not there, add a new String Value IsDomainMaster and set it to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Browser\ParametersĬhange the value of MaintainServerList from Auto to To set which computer is the Master Browser you need to make registry modifications on that computer. The computer that is the Master Browser is the only one that has the value To identify which computer is the Master Browserįor each computer in the Workgroup. Some people have third party devices on their network they can set to be the Master Browser, all non-1703 can browse. To work around the issue involves setting one computer to be the Master Browser. To work sometimes and not others, rebooting PCs forces a Master Browser election, which will change which PC is the Master Browser and can introduce the issue. If a 1703 PC is the Master Browser only that computer has Computer Browsing, if a non-1703 is the Master Browser all the non-1703 PCs have Computer Browsing. The service is broken in Windows 10 Creators 1703. So what we need now is either a great little tool to browse our networks that doesn't rely on SMB 1.0 or an upgraded Computer Browser service. Of course all Microsoft staff fit into these groups so the lack of browsing functionality in Workgroups is probably insignificant to them. Users who's data is in the cloud, on the internet have less issue, it may only affect attaching printer resources This does not affect AD users, those businesses which need to or have the luxury of being able to invest in server hardware and software. Locating and enabling printers becomes far more difficult without Computer Browsing.

The command "net view" allows us to quickly report which computers are available in the Workgroup and thereby use the information to run system reports and perform various tasks. Network browsing is an essential tool for doing a visualĬheck of which computing resources are available in a Workgroup. Not even spell checked and suggesting we only do it to access data we could map drives to, indicating a total lack of understanding as to why we need network browsing. From the linked article:įor home and small business users who use Network Neighborhood to locate Windows computers, you shoud map drives to the computers so that you no longer have to browse for them.
#WD MY CLOUD BROWSE IN EXPLORER UPGRADE#
The Computer Browser service relies on SMB v1.0, rather than upgrade the Computer Browser service so Workgroup users are still able to browse their networks they are They are getting rid of SMB v1.0, which is fair enough, it has real security issues.
#WD MY CLOUD BROWSE IN EXPLORER UPDATE#
SMBv1 is not installed by default in Windows 10 Fall Creators Update 2017 and Windows Server, Semi-annual Yes, that's right folks, after 25 years of being able to browse our networks Microsoft have decided Workgroup users don't need this functionality any more.

The Computer Browser service is broken in Windand is gone from future releases of Windows.
