Yes, certainly checked the WD version. It updates itself, anyway.
Not sure what fixed my sharing problem. It was OK up till 11 Apr so I restored my machine back to 7 Apr and all came right. So it must have been something altered in my PC - weird that it only affected the NAS, though.
Anyway, all backups to the NAS are going fine again.
Last edited by linw; 20 Apr 2015 at 14:56.
I'm seeing the same issue here. All of my Synology NAS shares haven't been reachable by my Windows 10 clients for a couple of weeks. I should add that this issue only exists for me over wireless connections. As well, my other windows server shares seem ok so this seems to be isolated to Synology shares (Linux\Samba?) only for me. Also, if I connect using an Ethernet cable then the shares are available again.
As others have mentioned, this is difficult to fix/troubleshoot given we don't have access to the Network Properties of our connection.
I've experienced this on an Asus N53SV Laptop and Surface Pro 3 running Windows 10. I had to restore my SP3 to Windows 8.1 as I needed wireless access to the shares from one of these clients.
Finally, I only run released builds and have upgraded to each new one as they've been released. Hopefully, a fix or new build will take care of this issue as a re-install from an ISO would take me a while given all my required apps.
Welcome to the forum, cipher. My main machine is cabled and now is fine with the NAS but I also have an older Toshiba laptop (win 10049 ISO install) on wifi and it is not seeing the NAS. I thought it was seeing it a few days ago, though!
A lot of us are keen to see the next release! Hopefully the network/sharing code will be in better shape.
I'm on build 9926 using a WD My Cloud which works perfectly on W7. I installed KB3032323, 3049508 and 3035132. Now the mapped drives prior to the WUP are red X'd and W10TP goes into a endless try to populate the system. If I close Explorer, it won't open again, IE, Chrome and MS Outlook won't open either.
This has been verified twice by restoring an image. I may try once more but removing the mapped drives first.
That sounds pretty drastic. Wonder why IE, Chrome and Outlook are failing?
I don't map drives. I use the //name convention. You could try that?
That might be because Explorer gets stuck during populating. It either hangs or takes forever to reboot after that also but I never waited it out but just force a powered down.
Didn't know there was another option. Any problem with apps that you use your NAS with that way or don't they care?
Can't use anything past build 9926 because WUP registry patch to hide an item breaks WUP. The forced AMD update breaks my apps.
Removing the network drives mapped by letter first, installed the three updates and remapped the drives seemed to work even held after a reboot.
Quote
