Windows 10: UNC seerver

Do I have to have a UNC server? It is making my computer too slow, so I can't work at home. Ever since I updated and restarted my Lenovo computer late last night, I'm having problems. When I tried to shut it down a few minutes ago it says my UNC is running in the background. I did not make it run,, so I want to know WHY it's on my computer and how it got there. My computer is only about 18 months old.

:)

 

For File Explorer, how to get UNC pathname of folder in mapped Drive ?

Thanks, this is another workaround.

If File Explorer can show the UNC Path, end-user only need to copy the address bar instead of

1. requiring CMD skill and memory for the command
   
2. additional four steps to get UNC pathname of a file.
   
   1. open CMD
      
   2. type in net use
      
   3. copy Remote text
      
   4. add subfolder to Remote Text
      

Your suggestion is very useful in general but for my case need more labour than the one I posted with help from

Find UNC path of a network drive?

Is it possible to minimize steps with your CMD option?

for example, open CMD in the subfolder instead and then type in some command to get UNC path of the subfolder?

There is a paid solution but I need approval from IT; which is unlikely because this is not commonly required except for communicating to Tech Support

Pay App

 

SharePoint - UNC designation of files

I am wishing to write directly to SharePoint using a windows based piece of software that is restricted to only being able to reference the UNC. The browser that is used at my organization is Edge, and I therefore am unable to see the UNC of a SharePoint file, which I believe you could do in IE 11.

Does anyone know if this is possible to do, or can suggest an alternative method. Basically I want to drop a file into SharePoint without using SharePoint interface available in Edge.

 

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.