Thus, remote access problems generally fall into one of four categories - namely: And finally, the remote access software itself must be properly configured and working. Furthermore, it requires that the user have account credentials necessary to operate the remote PC. Remote access hinges on a working network connection between the client and host. When, how, and why remote access goes wonky In this story I’ll focus on what you can do when you encounter problems making a remote connection work. See my story “ Windows 10’s Remote Desktop options explained” for more details about Remote Desktop and Remote Desktop Connection and how to use them. Thus, while there are plenty of third-party remote access tools readily available, many businesses (especially smaller ones) use Microsoft’s tools as a matter of cost-saving and preference. Remote Desktop Connection and Remote Desktop come built into Windows 10 and 11 at no added cost. The ongoing proliferation of “work from home” situations post-pandemic has only increased the value and importance of remote access. Network and support admins find this capability invaluable, particularly if they must access and interact with PCs (including those running Windows Server as well as desktop versions of Windows) in other locations. With some minor exceptions - usually related to applications or services that require direct, physical access to a specific machine (such as a BIOS/UEFI upgrade, firmware tools, and some OEM utilities) - one can do anything to a PC remotely that one can do directly.

Thus, for example, I can sit at my production desktop and access any of the other 11 PCs in my house easily and directly.

Both work to the same ends but have minor differences. Figure 1: Remote Desktop Connection (left) is more old-fashioned Remote Desktop (right) is a more modern app.

Anydesk remote desktop