Windows 10: Trouble with one windows 10 machine and mapped drive vs. UNC path.

Hello, I'm having trouble with one windows 10 machine and mapped drive vs. UNC path, but it's only with one user. the mapped drive let's call it J:\ is very slow to present the contents of the drive, sometimes a long as 20 seconds or more. The computer presents a progression bar in the address bar as if it is searching or indexing. By contrast my computer and any other one I try presents info virtually instantly. Here's what I know:1. This is a file share on a dedicated intranet TrueNAS fileserver.2. It does not matter if the user is directly connected in the office with ethernet or remo

:)

 

Drive Letter Mapping reverts to UNC path

When I use a mapped drive letter in an icon in Windows 10, if I check the Run as Administrator on the icon properties, the icon then reverts to UNC path instead of using the drive letter mapping. Of course, if I don't run as Administrator, I don't have
the permissions I need to run my program accessed by the icon.

 

One specific UNC path suddenly not working on one specific Win10 machine

Hi,

A month or two ago, my main computer stopped being able to access my NAS' UNC path (\\corbeau\...). It used to work.

• I do not remember changing anything on that NAS
• Other Win10 machines can access that same UNC path
• The problematic machine can access the NAS by using its IP in the UNC path (\\192.168.2.10\...)
• All machines can access other machines by their UNC path (\\cardinal\... or \\epervier\...)
• A ping for the NAS name from the problematic machine fails to resolve
• Pings from other machines work
• Every machine can ping other machines by their name

I'm totally lost. Where should I look for to resolve this very annoying issue?

Thanks.

 

Network Mapped drive is not accessible with Drive letter but accessible via UNC path through application

Issue: Applications are unable to access the files using network mapped drive letter but accessible using UNC Path

Azure VM

Windows Server 2022 Datacenter Azure Edition

Created a file share from Azure storage and mounted as network drive in Azure VM (using windows PowerShell command provided in Azure).

We are able to access the files via network mapped drive letter from VM (while we use RDP) and also through command prompt inside VM.

Applications are unable to access the files using network mapped drive letter. But applications are able to access by using full UNC path.

Kindly let me know what needs to be done to access using drive letters (Network mapped drive letters).