I got curios and I googled the error message.
A few of the resulting links look promising:
In short:
How many accounts do you have on the PC? (i.e. different users that log into the same machine with different passwords). Log onto each; and review credentials manager and disconnect any mapped drives.
Next I might try the HostFiles option.
Rebooting the Router, NAS, and PC won’t hurt as Bennor suggests
Win 10, with or without any mapped drives:
Hosts file has no entries, only comments.
One account per PC (I eliminated second ones earlier)
Riiiight.
So let me make sure I understand:
Netuse has been wiped.
There are (now) zero entries in Credential manager for either the Name of the NAS or the IP address of the NAS.
No shares are mapped to any drive letter on the PC
After you verify this; you should attempt to access one of the shares on the NAS. After you do this, then you should be able to access or map any share on the nas that has THAT SAME USERNAME and THAT SAME PASSWORD. And you will be unable to access any share that has a different username or different password. (this is regardless of wheter you chose to save passwords when you log on)
If this doesn’t work. . .I am out of ideas 
Verified. It looks like Netuse has not had any entries. and Credential Manager has nothing about the NAS or its IP.
Rebooted this PC, rebooted NAS, rebooted Router…
BUT… Can only access the shares that are “Public”
First try gives:
and an offer to try again:
Try again, and I get:
So… maybe it isn’t Credential Manager after all. “Windows Security?” I’ve got Norton for firewall…
I don’t think this is a norton issue.
(I also have Norton – - pretty sure it was running when I played with this sometime back)
Here’s a thought: Maybe its the public directory that is confusing things. One share is “public”; so it has no password. Then you are accessing a second share that does have a password. . . .and that creates the conflict.
Of course. . . I would expect this to bother ALL the PC’s. . .and not just one.
I presume all three PC’s are treating the network as “private”?
(I normally don’t have public directories on my NAS)
(and I am not in the same place as the NAS boxes at the moment; so I can’t play)
What happens if you use the My Cloud’s IP address rather than name to access and map a Share? Do you get the same error message?
Tried setting all shares’ Public to “off.” No help.
Yes, all PC’s are treating the network as private.
FYI, #3 & #2 are Win 10, #1 is Win 11. #1 & #2 are connected to server and router thru a switch. I have a WAP connected to that same switch. If I connect #3 through that WAP, no improvement.
#3 is normally wired directly to the router, to what looks like a built in managed switch.
Using IP address rather than “MyCloudPR4100” does not help – so I don’t think it’s a DNS issue.
Yes. Using IP address rather than “MyCloudPR4100” does not help – so I don’t think it’s a DNS issue.
One more thing: #3 (Win 10) does not see #1 (win 11) on the network, but it does see #2 (Win 10.) I have always thought this was because of Win 11. Any thoughts?
That’s an important clue.
the Win10 and Win11 machines should be able to see each other. . . and they should see each other bidirectionally.
Win10 and the OS/5 have “workgroup” functionality. If the PC’s and NAS are in different workgroups; that would cause such a problem. Note that a workgroup called “workgroup” and a workgroup of blank are different.
Maybe PC#3 has a different workgroup from PC#1, PC#2 and the NAS
Less likely: Check that all PC’s and NAS are in the same subnet (i.e. 192.168.xx.xx and 10.10.xx.xx are different subnets)
Then as NAS_user suggests check the “workgroup” name for all devices on the local network including the My Cloud and ensure they are all using the exact same workgroup name. And check that all devices are using IP addresses from the same IP address subnet range. If using any kind of AiMesh, Mesh nodes, power line extenders, WiFi extenders between the My Cloud and the computer experiencing the issue, move the PC and My Cloud so they are both directly connected to the same local network router.
Update: Got a new NAS (old one was rattling non-stop for days.) In the process of setting things up, I deleted the registry network drive mapping entries for all the mapped drives (on all 3 machines) and the credential manager entries for the old NAS, AND REBOOTED. Presto – machines 1 and 2 (Win 10 & 11) now see the new drives, I have mapped them and they are accessible in file explorer.
However, machine 3 (Win 10) “sees” the new NAS in file explorer, but cannot open to see the virtual drives. Gives the “incorrect user name / password” error.
The new NAS is a Synology, and the UI is a little different, and it allows file level access from the web interface, which I can do from all machines.
The only difference I can see (so far) is that #1 and #2 are connected through switches, but #3 is connected to the router’s own ports (which I think may be a built in switch.
All in “WORKGROUP” and same subnet 192.168.10.XXX.
In file manager, under Network:
#1 (Win 11) sees shared directories on #2 (Win 10) only. Sees #3 (Win 10) but cannot access folders, Sees NAS and folders. Sees itself.
#2 (Win 10) sees shared directories on #1 (Win 11), #3 (Win 10,) and, incidentally, itself.
#3 (Win 10) sees shared directories on #2 (Win 10) ONLY. Sees itself. Sees NAS, but cannot open it: “The user name or password is incorrect.”
If you are trying to access another Windows PC then that is an entirely separate issue and unrelated to the My Cloud PR4100. You would have to configure the other Windows PC to allow Sharing of it’s hard drive and folders on it’s hard drive. If you hare having issues with accessing the Synology NAS that is really a question that is better addressed over on Synology’s support forum(s) rather than it’s competitor Western Digital.
If you are getting a error accessing the My Cloud PR4100, what is the specific error message?
Standard note: On a Windows PC sign-in account, it typically does not support multiple usernames and passwords trying to access the same network NAS and network Shares. Instead it expects to use only a single username and login for a NAS network share per Windows sign-in account.
" On a Windows PC sign-in account, it typically does not support multiple usernames and passwords trying to access the same network NAS and network Shares. Instead it expects to use only a single username and login for a NAS network share per Windows sign-in account."
How can I investigate / fix this?
OK - - - I agree with Bennor - → This smells like a Windows Network setup problem; NOT a nas problem.
Let’s start simple: It sounds like you have three users. Let’s call them User1, User2, and User3.
Let’s presume that on NAS-WD. . .you have Share-WD1 for user 1, Share-WD2 for User 2 and Share-WD3 for user 3.
Let’s presume that the OTHER NAS is NAS-SYN, with Share-Syn1 for user 1, Share-Syn2 for user 2 and Share-Syn3 for user 3.
If User 1 is using PC1, User 1 can access Share-WD1 and Share-Syn1. HOWEVER - - - once User 1 enters credentials. . . nobody will be able to access Share-WD2 or Share-WD3 if the credentials for logon are different. Also, nobody will be able to access Share-Syn2 or Share-Syn3 for the same reason.
If User 2 is using PC2, User 2 can access Share-WD2 and Share-Syn2. HOWEVER - - - once User 2 enters credentials. . . nobody will be able to access Share-WD21or Share-WD3 if the credentials for logon are different. Also, nobody will be able to access Share-Syn1 or Share-Syn3 for the same reason.
The credentials are stored in the credential manager of windows.
If you want a user to have access to multiple shares; you need to grant permissions from the NAS. In other words, you have to assign read/write access to each user for each share. In other words, in the WD NAS setup; Share-WD1, Share-WD2, and Share-WD3 must be accessible to User 1. Then, when user 1 accesses the NAS, they will have the ONE set of access permissions to the NAS, and the NAS will allow them to access the three shares.
So you want User 1 and User 2 to have access to Share-WD1, Share-WD2 and NOT Share-WD3, then you need make those particular settings changes in the NAS.
In my house, I keep it simple by having a single user. All the PC’s have the same login credentials, and the NAS units have a single User which has access to all the shares. Things only get tricky if you need to segregate or restrict access of specific shares to specific users.
Sharing Folders between windows folders is slightly different.
Done all that, except for having only one user. Thing is, it used to work fine.
Also, I just changed WORKGROUP to WORKGROUP2 on the 4100, the Synology, and on pc 1. File manager can see the 4100 directories now, but not the Synology’s. And, pc 2 can still see everything, with it’s creds. Changed both back to WORKGROUP, can still see 4100 directories, but not Synology’s.
Changed Synology to use SMB 1, as well as 2 and 3… All is well for NAS’s in File Explorer. Still can’t see other pc’s directories, but that is a problem for another day.
Seems like there is somewhere else, other than Win Creds, that is saving logon credentials.
Guess I’ll continue on Windows forums.
As previously explained that is an entirely separate issue that is unrelated to the My Cloud PR4100. If you haven’t done so already you would need to configure file sharing on the Windows OS itself to allow for other computers to access a Windows hard drive and access it’s contents. One can find various guides on how to setup file sharing on Windows 10 and 11 by doing an internet search. For example:
File sharing over a network in Windows
How to Share Files and Folders Over a Network in Windows 10 and Windows 11
How to Share Files With Others in Windows 10
How to Share Files in Windows 10/11.
Found the solution to the NAS access problem. Worth noting that is was, sort of, a NAS “problem.” Actually more of a “feature.” Old NAS working fine - new NAS not accessible from Win 10 Home machine.
Fixed.
1 - Upgraded to Win 10 Pro (was Home) to enable access to Group Policy Editor
2 - Use “Start->Run” and type in “gpedit.msc” in the “Run” dialog box. A “Group Policy” window will open.
3 - Click down to “Local Computer Policy → Computer Configuration → Windows Settings → Security Settings → Local Policies → Security Options.
4 - Find the policy “Network Security: LAN Manager authentication level”.
5 - Right click on this policy and choose “Properties”.
6 - Choose “Send NTLMv2 response only/refuse LM & NTLM”.
7 - Click OK and confirm the setting change.
8 - Close the “Group Policy” window.
So, what is the difference between a “bug” and a “feature?” A bug is a cockroach. A feature is a cockroach in a tuxedo.
That’s all folks.
| Forums | News and Announcements | Register | Help | Forum Guidelines |
Copyright © 2021 Western Digital Technologies, Inc. All rights
reserved.
|
Trademarks
|
Privacy
|
Community Terms of Service
|
Site Terms of Use
|
Copyright
|
Contact WD
|
