Unable to map Network Shares Windows 10

Hi,
I've got 2 Western Digital Network drives hard wired on my network, a My Book World and an EX2.


Since upgrading to Windows 10 I've had intermittent problems viewing and setting network drives. I've read a lot of other posts and tried a number of things suggested without success. WD Support have run out of ideas.

The WD Discovery tool finds the Network drives, but the box to map network drive is greyed out. I can access the desktop control panel from my browser. If I try to add a network location the drives are not listed. If I try to add the drive letter \\WDMYCLOUDEX2\Public the network path is not found?

I have another Windows 10 computer on the network which can access the drives without issue - so it must be a setting on my PC. Tried disabling my Kaspersky security - still not being seen?


I suspect that this has been as a result of a windows upgrade?

Anybody had similar issues?

Well would you believe it;

My computer has just updated itself to Windows 10 Pro Version 1511, OS Build 10586.3 and the drives are showing again.
I knew it was something to do with a previous update.............

Whew!

I have a network with 4 notebooks, 3 android mobiles, 2 WD external ethernet hard drive, 1 WDTV Live. After upgrade to Windows 10, when I click to "Network" (On Windows Explorer left panel), I can not see nothing. The computer can not see even itself. I have been searching in foruns and a lot of people are talking about this Windows 10 bug. I have tryed to configure the network using the router (DLink dir635) and the modem Humax. Nothing. The curious is: I have 3 notebooks with Windows 10. If I turn them all off and turn off the router, after turn on again, the first computer the see the shares, but the others can not. Other people talk in foruns about this problem. My problem is not only makes Windows 10 see My Cloud and My Book Live, but get back my home network Windows 10 get way. In the beginning, I thought the problem was with the Windows 10 version. I have one notebook Windows 10 (10240) that work perfectly well and two notebooks with Windows 10 (1511) that did not. After, I discover that, as I do not turn them off, the diference was not the Windows 10 version, but the fact the notebook with Windows 10 (10240) was the first turned on in the network. As I explained before, when I turn them all off, if I turn one notebook with Windows 10 (1511) [November Update] it will work perfectly well, but only the first turned on.

The reason the first comp to get turned on sees shares is that this first one becomes the Master Browser and the Master Browser isn't affected by the discovery problem.

Discovery, particularly if you have Linux NAS boxes as well, is broken. We have to wait for MS to fix what they broke with 1511.

Yes, I know, it is pretty darn frustrating.

linw said:

The reason the first comp to get turned on sees shares is that this first one becomes the Master Browser and the Master Browser isn't affected by the discovery problem.

Discovery, particularly if you have Linux NAS boxes as well, is broken. We have to wait for MS to fix what they broke with 1511.

Yes, I know, it is pretty darn frustrating.

Linw, I wonder why the hell Microsoft is sleeping for so serious problem. I bought a new computer only to use Windows 10. The old one was not compatible (some problem with the video drive), it uses Windows 7. So I bought a new Dell notebook with Windows 8.1 and the promise to update freely to Windows 10. I had to downgrade to Windows 8.1, because I need access my drives. Now I have to use Windows 8. I just HATE Windows 8. It's ugly and not practical.

No idea why MS is asleep on this one. They must know how to fix it as they broke it! Many have outlined what the problem is but still no response from MS.