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?