Windows 10: 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?

:)

 

RDP

Hi Nikki,

We can see here that you are having issues using (RDP) Remote Desktop Protocol on your computer. There are several reasons why you are experiencing this concern. To set your expectation, we will be doing some troubleshooting steps to isolate
this problem. Before we proceed, may we know the following:

• Any changes made on the computer prior to this concern?
• What troubleshooting steps have you tried so far?
• Is this the first time that you encountered this problem?
• When did you notice about this issue?
• Can you send us a screenshot with the error message that you are getting? Note: Please do not include any personal information.

 

RDP

• Any changes made on the computer prior to this concern?
  
  Initially when we received the problem there wasn't any changes made on the computer since we couldn't figure out the problem, we upgraded the pc to windows 10. It fixed the problem momentarily and then it starts again. Then we re initiated the upgrade the
  same day I wrote this post and it was fixed again and then on today the issue is back

• What troubleshooting steps have you tried so far?
  
  In the past we would delete the MS Licensing Protocol folder as suggested by so many other posts and restart the RDP connection ad administrator to rebuild it. This time around it didn't fix anything. Like I said previously we've tried to upgrade the PC and
  the fix is temporal

• Is this the first time that you encountered this problem? No

• When did you notice about this issue? I'm not sure when it started because I haven't been on this project that long but I would say within the last month based on me. Based on other conversations this has happened in the past.

• Can you send us a screenshot with the error message that you are getting? Note: Please do not include any personal information.
  
  Sure
  
  

 

Things to do once connected new G-Sync monitor

I'm getting my G-Sync monitor today.

I think I have to take the following steps:

• Connect 1440p G-sync monitor with DP cable
• Connect second 1080p 60Hz monitor by HDMI
• Startup PC
• Reinstall display driver
• Restart PC (I always do that after display driver install)
• Activate G-Sync in NV control panel (I believe also V-Sync is auto on after that?)
• Set my 1440p monitor from 1080p to 1440p
• Calibrate my 1440p monitor

Also ingame, I should turn off V-Sync?
Are there any problems running a second 60Hz 1080p monitor?

Is there anything else I should do/know?