Mybooklive не виден в сети windows 10

1. Can no longer access WD MyBookLive through «This PC» on Windows 10.

   Since the latest major Windows 10 update, I can no longer access my Western Digital MyBookLive through «This PC». There are also other problems associated with this issue.

   I can create «Network Locations» to the shared folders but there are file size restrictions when using this method. I can no longer copy back any stored ISO images from the drive and get an error saying the file is too large.

   I can no longer mount ISO images from my «MyBookLive» of my software installation disks.

   I am very frustrated and am considering going back to the old Creators Edition of Windows 10.

   How can I fix these problems?

   

   

   

   

2. No longer can access folder off of WD Network Drive

   I mistakenly changed the security settings for a specific folder on my WD LiveBook network drive through windows explorer by right clicking on the folder, going to security tab and removing all groups / users attached to the folder. Now I can no longer
   access the drive no matter what I try. I get the following error:

   Network Error

   Windows cannot access \\MYBOOKLIVE\Folder_Name

   You do not have permission to access \\MYBOOKLIVE\Folder_Name. Contact your network administrator to request access.

   For more information about permissions, see Windows Help and Support.

   I have go back to the folder and tried to re-establish user rights to the folder through the security tab, but the security tab no longer shows up, or if is does, states I do not have permission to add users. I have also gone out to the WD live Access
   and changed the security setting there to be completely open. Still no luck. 3 hrs on the phone with Microsoft and not dice. Help!

3. After the last major Windows 10 update, my computer can no longer access MyBookLive NAS.

   After the last major Windows 10 update, my computer stopped being able to access my Western Digital MyBookLive NAS.

   I can create network location links under «This PC» as long as I specify a specific folder on the MyBookLive, but I can no longer access the main folder location of «\\MyBookLive\».

   I checked my settings under «Turn Windows Features on or off» and the SMB settings were disabled after the update. I turned them back on, and no difference, it still will not access anything on the NAS without creating links to specific folders and entering
   a user name and password. I did not have to do that before.

   What can I do to fix this?

   This is the error I get:

   —————

   Windows cannot access \\MyBookLive\

   Check the spelling of the name. Otherwise, there might be a problem with your network. To Try to identify and resolve network problems, click Diagnose.

   —————

   Issue found

   The remote device or resource won’t accept the connection.

   Contact your network administrator

   —————

   The device or resource (MyBookLive) is not set up to accept connections on port «The File and printer sharing (SMB)».

4. Can no longer access WD MyBookLive through «This PC» on Windows 10.

   Windows 10 Tweaks

   Pressing “Windows+Pause Break” (it’s up there next to scroll lock) opens the “System” Window.

   Windows 10: In the new version of Windows, Explorer has a section called Quick Access. This includes your frequent folders and recent files. Explorer defaults to opening this page when you open a new window. If you’d rather open the usual This PC, with links to your drives and library folders, follow these steps:

   • Open a new Explorer window.
   • Click View in the ribbon.
   • Click Options.
   • Under General, next to “Open File Explorer to:” choose “This PC.”
   • Click OK

   credit to Lifehacker.

BobArch2

BronzeLounger

Posts: 1237

Joined: 25 Jan 2010, 22:25

Location: Pickering, Ontario, Canada

StuartR

Administrator

Posts: 12439

Joined: 16 Jan 2010, 15:49

Location: London, Europe

The Computer Browser service is broken in Windows 10 1703 and is gone from future releases of Windows.

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.  This article from Microsoft explains:

SMBv1 is not installed by default in Windows 10 Fall Creators Update 2017 and Windows Server, Semi-annual
Channel

They are getting rid of SMB v1.0, which is fair enough, it has real security issues.  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
simply removing it.  From the linked article:

For 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.

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.  Network browsing is an essential tool for doing a visual
check of which computing resources are available in a Workgroup.  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. 
Locating and enabling printers becomes far more difficult without Computer Browsing.

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.  Users who’s data is in the cloud, on the internet have less issue, it may only affect attaching printer resources
which can be worked around.  Of course all Microsoft staff fit into these groups so the lack of browsing functionality in Workgroups is probably insignificant to them.

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.

The service is broken in Windows 10 Creators 1703. 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.  This is the reason why browsing appears
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.

To work around the issue involves setting one computer to be the Master Browser.  Some people have third party devices on their network they can set to be the Master Browser, all non-1703 can browse.  To identify which computer is the Master Browser
you can run the command 

nbtstat -a ComputerName

for each computer in the Workgroup.  The computer that is the Master Browser is the only one that has the value

__MSBROWSE__

in the list.

To set which computer is the Master Browser you need to make registry modifications on that computer.  Browse to the registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Browser\Parameters

Change the value of MaintainServerList from Auto to
Yes

If it is not there, add a new String Value IsDomainMaster and set it to
True

You may need to reboot to activate this.  If you want to be absolutely positive no other PC takes the Master Browser role you can set the value of
MaintainServerList from Auto to No on all other PCs in the Workgroup.  You may even find that a non Microsoft third party device on the network attempts to take over the Master Browser role.

I re-iterate that this is just a short term workaround, Computer Browsing for workgroups is history for Windows 10.  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.

• Proposed as answer by

  Friday, September 22, 2017 12:59 AM