Hello,
Users from a single location are experiencing major issues connecting to our RDS server. There are 3 locations, one main site where the server is location on the same subnet, another site south, and another site to the east. The south and east sites are connected with a VPN connection. Only users at the east site are not able to connect well to the server. I can check event viewer logs and I once saw something with winlogon stopping but I always see the error "session 14 has been disconnected, reason code 0" and "session 14 has been disconnected, reason code 5" from the east site subnet. I did a netstat to see that users are connecting with TCP 3389. An RD Gateway is not configured. I can connect to the RDS server for hours and have no problems. Error code 0 means No additional info is available and 5 means client's connection was replaced by another connection. I am not sure what would be doing this.
I was thinking like some kind of time but I sent all of the timeout settings on the server to never. I thought maybe it was a UDP socket timeout that was acting weird over that single connection but with netstat -a | findstr ":3389" I only see TCP ESTABLISHED sessions and only listening on UDP 3389.
Update KB3000850 is installed which replaced KB2984006 update for windows server 2012 R2 that fixes RDS issues like this. Clients are Windows 10.
Any help would be appreciated.