Cannot access ReadyNAS Duo from Windows 11

[ndunlavey]

Since I upgraed to Windows 11 I cannot access my ReadyNAS Duo from Windows.

If I try to open a mapped share in File Explorer I get an error:

---------------------------
Restoring Network Connections
---------------------------
An error occurred while reconnecting U: to
\\henrietta\userdocs
Microsoft Windows Network: The local device name is already in use.

This connection has not been restored.

Right clicking the mapped drive gets me a whirling circle for a few seconds and then nothing happens.

I can ping the IP address (192.168.3.11) and the "symbolic" name from acommand prompt OK.

Raidar doesn't detect the device (although it does detect another ReadyNAS on the network OK)

Using a browser to go \\192.168.3.1 says:

Your file couldn’t be accessed

It may have been moved, edited, or deleted.
ERR_FILE_NOT_FOUND

ANyone got any ideas?

Is there a way I can take the drives out to retrieve the data and then factory reset the ReadyNAS?

[StephenB · Accepted solution]

---

@ndunlavey wrote:

An error occurred while reconnecting U: to
\\henrietta\userdocs
Microsoft Windows Network: The local device name is already in use.

What happens if you run CMD and enter

net use * /delete /y
net use U: \\henrietta\userdocs

Be careful on the typing, especially the two different slash directions.

If that fails the same way, try

net use * /delete /y
net use U: \\henrietta\userdocs /user:admin nas-admin-password

useing the real NAD admin password of course.

[StephenB · Accepted solution]

---

@ndunlavey wrote:

An error occurred while reconnecting U: to
\\henrietta\userdocs
Microsoft Windows Network: The local device name is already in use.

What happens if you run CMD and enter

net use * /delete /y
net use U: \\henrietta\userdocs

Be careful on the typing, especially the two different slash directions.

If that fails the same way, try

net use * /delete /y
net use U: \\henrietta\userdocs /user:admin nas-admin-password

useing the real NAD admin password of course.

[ndunlavey]

Oh, wow!  Yes, that (the first option) has fixed it - thanks so much, Stephen 🙂