NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Jimmah
Sep 11, 2016Aspirant
Windows 10 Network discovery broken after 6.5.2 update
Today I decided to set up some ReadyCloud shares, and discovered I needed to update my firmware to do so. The NAS then updated itself to 6.5.1. Pretty much everything (including the new cloud sha...
- Sep 12, 2016
I see your logs are being flooded with messages relating to the WSD discovery service. I have sent you instructions on how to update to a newer version of this service.
It looks like you used to have two volumes and the NAS still has references to the volume you destroyed in its config which should be cleaned up.
Jimmah
Sep 12, 2016Aspirant
Apologies! All machines were indeed on WORKGROUP, but I did not realise the NAS also had a workgroup name set. I changed this to WORKGROUP, and even restarted the NAS, but no joy.
I've just sent the logs.
It's mainly an annoyance now that I've worked out mapped drives work fine.
mdgm-ntgr
Sep 12, 2016NETGEAR Employee Retired
I see your logs are being flooded with messages relating to the WSD discovery service. I have sent you instructions on how to update to a newer version of this service.
It looks like you used to have two volumes and the NAS still has references to the volume you destroyed in its config which should be cleaned up.
- JimmahSep 12, 2016Aspirant
It's fixed now, unfortunately it's late here in N.Z. and I didn't think to check between stuff, so it's one/more of:
* the updated WSD discovery service
* disabling IPv6
* cleaning up the volume config, if that had already been done via remote admin
My money's on #1
Thanks mdgm, much appreciated =)
- mdgm-ntgrSep 12, 2016NETGEAR Employee Retired
I would think it is #1 too.
#3 was just something that should be done.
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!