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

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?

:)

 

Mapped Drives Issues

To clarify .... the issue is the Windows 10 OS. It is with Windows File Explorer. The Mapped drives used to appear in File Explorer's left panel list of drives and folders. Two days ago File explorer stopped show the mapped drives. so not they don;t appear in the list of Drives and folders.

- - - Updated - - -

I did, it has no effect. I also check the NAS devices they support SMB 2.0. Also I have several other computers on my home network they work fine with the mapped drives and They do not have SMB 1 turned on. So it is something that happened to the computer in question.

 

NAS Disappears and "net view" Fails on non-First Computer to Boot

With the latest build of Win10 (Version 1703, Build 15063.138), our NAS has disappeared from the Network portion of File Explorer on the last of our two computers that boot. Trying to do "net view" from a PowerShell (Admin) window works on the first computer
booted, but on the second it fails with the useless error 2184: "the service has not been started" (and it's more than useless "net helpmsg 1284" suggestion which merely repeats the same worthless phrase). Reversing the boot order reverses the computers
that succeed and fail with "net view". The computer that boots first becomes the Master Browser and is the only one that can see the NAS in the Network portion of File Explorer. On both computers, the mapped Z: drive to the NAS always works and browsing
to the NAS' IP address or hostname works just fine. It's just not showing up in Network.

Feedback Hub link

 

Can't see NAS (SMBv1), even via IP address (tried common solutions)

I have a DLINK DNS-325 NAS which worked fine until this week.

• The issue started after I performed an in-place upgrade. (To fix an unrelated Windows Store problem.)
• I restored the NAS to factory settings and manually rebuilt its settings.
• I can access the NAS's Web-based UI without a problem and it reports no errors. I can also ping it without any error.

I have tried several solutions, some from "My nas devices are not showing in Windows File Explorer - Network, Windows 10 version 1703, build 15063.332" for example.

• Network reset
• Enabled SMBv1
• Forced my PC to be the Master Browser
• Force-enabled "Enable NetBIOS over TCP/IP"

To take Windows networking out of the equation, I'm initially trying to access the NAS by its static IP, 192.168.*. In the command window:

• I can ping it without problem
• `net view \\192.168.*` gives an error 53.

What should my next steps be? Thanks.