I just found out I can no longer access my PR4100 on network. I think this is something to do with the recent upgrade to Windows 24H2. Is this a know issue, and is tthere a fix?
Do you mean log into the dashboard or connect share drives?
I can log into dashboard fine. The shares connect will not work. Even if I try to connect in the network tab of Windows explorer using file path of \SERVERNAME\ it then asks for user name and password, which I give it, tthen it does not recognise it.
I can log onto it on my Macbook no problem though.
So there’s an issue with 24H2. MS decided to enforce SMB signing and disable Guest fallback.
Here’s a recent thread on this.
In it, there are links to “workaround” the issue.
Hello @Saudade I found that earlier and have just applied the fix, ie enable guest fallback. It now works as it did. This seems to affect other NAS as well, including Synology. The difference being with them is that their software keeps up to date and allows SMB signin on the server.
I hoope that WD sorts this out in a future OS update.
Thank you
Glad you “fixed” it. No telling when WD will get around to it.
I’ve had to do this with my EX4 and my older Netgear ReadyNAS. Both are firewalled in my local LAN so I have no issues with this fix. My primary PC is still 23H2 but I’ve tested 24H2.
Ah, okay. How are they firewalled? Using something other than just Windows firewall?
I am not too worried as its just me and my wife ever on the network, but Id like to be as secure as possible. Any tips there do let me know.
Thanks
Just my network router. I don’t use the My Cloud “portal” for access from the internet so they’re only accessible on my home network. No other integration with any cloud service either (One Drive, Google Drive, Dropbox, etc.).
There indeed has been a change in Win11 24H2 release.
We have been slimed by Microsoft:
Control SMB signing behavior | Microsoft Learn
We have indeed been hosed by Microsoft.
I would not hold your breath waiting on a fix from WD on this topic.
After upgrading to Windows 24H2, you might have trouble accessing your WD My Cloud PR4100 on the network. This could be related to changes in SMB protocol settings or network discovery settings made by the update.
First, check your PR4100 settings in the dashboard and make sure it supports SMB2 or SMB3. This can be found under Network settings. If needed, adjust the settings and restart the device.
On your Windows machine, open the Services window (services.msc
) and ensure that Function Discovery Provider Host and Function Discovery Resource Publication are set to Automatic (Delayed Start) and are running. After making these changes, restart the computer.
If the PR4100 still isn’t accessible, try mapping the network drive using the device’s IP address and share name in File Explorer. Make sure to enter the correct network path.
Finally, make sure your PR4100 is running the latest firmware, and remove any saved credentials in Credential Manager to re-establish the connection. If the issue persists, contact Western Digital support for further help.
Excellent, thanks very much Ken. I can confirm that this works for me. I have applied those changes in the services window. I can now access my mapped drives again.
Before this I had gone the route of this:
On the Start Menu search, type gpedit and start the Edit Group Policy app (i.e. Local Group Policy Editor).
b. In the console tree, select Computer Configuration > Administrative Templates> Network > Lanman Workstation.
c. Double-click Enable insecure guest logons
d. Select Enabled > OK
I have now gone there again and set insecure guest logons to OFF and I can still get in okay.
Thank you very much for your help. Happy hols.