windows 2012 r2, hyper-v, clients connect via rds website and then launch a rds session (vdi windows 10 vm). It was working, but then a few users reported being unable to connect. Silly me, I figured "apply latest updates and reboot" and now no
one can connect. I updated and reboot the RDS and Hyper-V server (RDS is actually a VM running on the same Hyper-V server).
From the RDS server's RemoteDesktopServices-RDPCoreTS log a connection looks like this:
Event ID 131, the server accepted a new TCP connection from client blah blah blah
Event ID 65, Connection RDP-Tcp#0 created
Event ID 141, PerCounter session started with instance ID 0
Event ID 133 the following network characteristics have been detected for tunnel 8;...
Event ID 132, a channel rdplic has been connected between the server and the client using transport tunnel 0
Event ID 132, a channel rdpcmd has been connected between the server and the client using transport tunnel 0
Event ID 98, a TCP connection has been successfully established
Event ID 100, the server has confirmed that the client's multi-transport capability. (really bad English there BTW)
Event ID 130, the server has initiated a multi-transport request to the client, for tunnel 1
Event ID 130, the server has initiated a multi-transport request to the client, for tunnel 3
Event ID 135, the multi-transport connection finished for tunnel 1, its transport type set to TCP, reason code 3 (no UDP packets received)
Event ID 135, the multi-transport connection finished for tunnel 3, its transport type set to TCP, reason code 3 (no UDP packets received)
Event ID 103, the disconnect reason is 1033
Event ID 102, the server has terminated main RDP connection with the client
I've found articles about RemoteFX and disabling it via GPO and registry values - which I tried to no avail.
HELP!!! please!