OS5- Unable to map Private folders vs Public folders Win10

This is a common headache because OS5 handles SMB (Windows file sharing) differently for private shares compared to the default Public share. Let’s go step by step:

🔹 Why It Works for Public But Not Private

Public folders can be mapped without credentials (guest access).

Private folders require a valid My Cloud user account (username + password).

Windows 10 sometimes caches old/guest credentials, which causes login failures when switching from Public to Private shares.

✅ Step 1: Remove Old Credentials

On Windows 10, open Control Panel → Credential Manager → Windows Credentials.

Look for any saved entries for your My Cloud (e.g., \\MYCLOUDEX2ULTRA or its IP).

Remove those entries.

This ensures Windows won’t try to auto-login with the wrong credentials.

✅ Step 2: Map the Network Drive Properly

Open File Explorer → This PC → Map network drive.

Choose a drive letter (like Z:).

In the folder field, enter the UNC path:

For Public share:

\\MYCLOUDDEVICE\Public

For Private share (example “Jacob”):

\\MYCLOUDDEVICE\Jacob

(You can also use the IP, e.g. \\192.168.1.25\Jacob)

Check Reconnect at sign-in.

Important: Check Connect using different credentials.

When prompted, enter:

Username: the My Cloud user name (not your Windows login).

Password: the password you set in the My Cloud dashboard for that user.

✅ Step 3: Avoid Mixed Connections

Windows 10 cannot connect to the same NAS with multiple users at once.

Example: If you’re connected to \\MYCLOUD\Public as guest, you won’t be able to connect to \\MYCLOUD\Jacob with credentials.

Fix: Disconnect all network drives first:

net use * /delete

Then map only the Private share with credentials.

✅ Step 4: Adjust Windows & OS5 Settings

In WD My Cloud Dashboard → Settings → Network, make sure SMB protocol is enabled (SMB2/SMB3 is recommended; SMB1 should be avoided unless necessary).

In Windows Features, ensure SMB 1.0/CIFS File Sharing Support is unchecked (unless you’re troubleshooting older devices).

If mapping still fails, try using the device IP address instead of the hostname.

🔍 Quick Test

Try opening a run dialog (Win+R) and typing:

\\MYCLOUDDEVICE

or

\\192.168.x.x

Windows should prompt for login. If it doesn’t and just opens Public, cached guest access is the problem → clear credentials again.

✅ Summary:

Public shares connect without credentials.

Private shares require My Cloud user credentials.

Windows can’t mix guest + user sessions, so clear old connections before mapping private.