Can't map NAS by IP in File Explorer, but with NET USE in cmd

WTenNewbie · 09 Nov 2020

Since some days I can't map a NAS Share by IP anymore, but only in the windows 10 file explorer.
If I execute a NET USE for the same IP and the same Sharename (using the same username and password), it works fine.
Example:
\\192.168.1.50\Series

I can also map the same NAS by it's name (Example "MyNAS\Series") in the file explorer. Therefore I don't think that a wrong username, wrong password or any access right problem is the cause.

Why should the Windows 10 Pro (b2004, 19041.572) file explorer not let me map a drive by IP anymore?

Additional informations:
If I map a first share by its NAS-name successfully and then try to map another share from the same NAS with another user in the command line with NET USE, I get a
"System error 1219 has occurred"
On my other PC (Windows 10 Pro b1909, 18363.1139) I can connect two shares from the same NAS (one by NAS-IP and one by NAS-Name) without any problem.

Is it not possible anymore to map 2 shares from the same NAS with 2 different users, using 1 x IP and 1 x NAS-name?

swarfega · 09 Nov 2020

So if you type \\192.168.1.50 into file explorer, then right click on it and choose map drive, that doesn't work? How old is the NAS?

WTenNewbie · 09 Nov 2020

That doesn't work and results in "System error 1219 has occurred."
The Synology NAS has the newest available "DSM 6.2.3-25426 Update 2" installed.

In the meantime I found a possible reason:
On the NAS itself there have been a "ghost connection" from the user not able to create a new map anymore. This connection remained there even after several reboots of my Windows 10 PC. I have manually deleted this connection on the NAS.

Currently I can connect as wished from file explorer and NET USE. If this continues for a few days, I will mark the problem as solved (without knowing, why this "ghost connection" was established).