Windows 10: RDP windows 10 clients to windows 10 Pro rdp host disconnect momentarily many times per day

I have several windows 10 PCs in 2 different offices that remote into my local windows 10 Pro PC via RDP. The remote PCs get disconnected and almost instantly reconnected (less than 2 seconds) several times per day. There is no VPN, just the default Windows 10 firewalls and each location has 300/25 internet. Several times per day the clients get a disconnect notice and then it reconnects and everything is fine again. This is very annoying. Anyone have any suggestions? Thanks!

:)

 

Windows 10 1709; host sleeps during active RDP session

I am reporting a bug/oversight.

HOST OS:

Windows 10 64-bit Version 1709 (OS Build 16299.192)

HOST SETTING:

Set to sleep after 2 hours of inactivity

PROBLEM:

Host computer sleeps after 2 hours of inactivity even when a client is connected via RDP (Remote Desktop)

DESCRIPTION:

In previous versions of Windows and even in Win10 before the Fall Update an active RDP session has always prevented the host computer from entering a sleep state even when set to do so after X minutes of inactivity. Since the Fall Update the host computer
of an active RDP session will sleep during an active RDP session when there is lack of activity on the client computer. There should never be a reason for the host of an active RDP session to enter sleep mode when there is a client connected. If the client
computer is set to sleep after X minutes of inactivity it seems natural it should do so even during an active RDP session, but then, and only then, should the inactivity timer start for the host computer.

HISTORY:

There was a bug introduced in Remote Desktop sometime prior to Win10 Fall Update wherein a host computer would not sleep when set to do so after a period of inactivity after a client had connected and subsequently disconnected to the host via RDP. This
was finally fixed in Fall Update, but I have a sneaking suspicion the fix was too aggressive and this is what led to the problem I am reporting.

Sean

 

WIndows 10 Pro will not accept RDP request

I recently installed Windows 10 Pro on one of my VM host. My plan was to use it as a management box to RDP into when I am traveling. I currently have a Windows 7 VM that I use for this purpose but wanted to decommission it for something newer. However
I have been having issues connecting to the Windows 10 Pro VM via RDP unless the VM is already logged in. Currently I have to connect via vSphere Client login to the Windows 10 Pro VM via the console view and then I can connect via RDP. If the machine logs
out at any point I have to connect again via vSphere Client and login again before RDP will respond to any request. If anyone has any ideas I would appreciate it. I was hoping to have decommissioned the Windows & VM by now but I am going to have to wait until
I have been able to reliably connect to this new management console.

 

RDP syncing?

I connect to one terminal server running Windows Server 2012 R2 from two Windows 10 machines. (I connect from Macs, too, but they don't share this issue.) I connect to the server with Microsoft's RDP client that is native to Windows 10. Both Windows 10 machines
have local authentication; neither one syncs with a Microsoft account for login purposes (although both have OD, ODFB, and an O365-based installation of Office). Both machines log in to the same account on the server; there is never a time when both Win10
machines are logged in to the server at the same time.

The terminal server is running on AWS. In order to get to the server, I have to either go through a Bastion host--in which case the terminal server has one IP address--and then log in through RDP; or log in directly via RDP, in which case the terminal server
has a different IP address.

If I have logged in with one IP address in RDP from one of the machines, that address will be the default address in the RDP client on the
other machine, even if my last login on that machine was to the other IP. Same in reverse; if I log in with one IP address in the RDP client, that's the address that first appears in the RDP client of the other machine, even if it hadn't been used
on that machine.

That means that somehow, somewhere, something is syncing between these two RDP clients. What is it?