# Is there a reason for mapping a network drive that was also being remotely accessed through Network Sharing by the same PC?

Is there a connection/reason for mapping a network drive and Network Sharing that same PC? Both PCs run Windows 10 Pro. Because a PC that has been remotely accessing mine, through Network Sharing and Remote Desktop, has mapped the network drive of my PC also. What would the reason be for this?

• Some programs may be written in ways or with code libraries that do not support UNC pathnames (\\server\resource), and require "classical" drive/directory pathnames (C:\path\to\file). To accommodate such programs, one would have to map a drive letter to the connected UNC resource. Apr 23, 2021 at 12:09
• Even using Windows 10 Remote Desktop? what would be the point? The reason? Does it make future remote access easier/quicker? Apr 23, 2021 at 12:12
• (1) You didn't mention Remote Desktop in your question. (2) Remote Desktop essentially turns the remote computer into a keyboard and screen to your computer. That's not "network sharing". If the other computer wants to run programs on itself, but access data that is stored on your computer, that would use network sharing, and the programs being used may be the type of program that I was referring to in my first comment. Apr 23, 2021 at 12:17
• My error sorry. Both Remote Desktop and Network Sharing have been used to access mine. Am I correct in thinking that mapping my network drive basically puts it in the remote PC’s drive? Apr 23, 2021 at 12:19
• It doesn't put anything on the remote computer; it merely establishes a local legacy-style alias to the network resource - that is, if I map Q: to \\yourcomputer\somefolder, then a program running on my computer that doesn't understand UNC pathnames can still access \\yourcomputer\somefolder\thatfile as Q:\thatfile. The file is still on yourcomputer, not mine, but it's accessible as though it were on mine. Apr 23, 2021 at 12:23