![]() I had a similar issue using remote resources, published remote app would load fine however when left idle, after 60~ seconds it would freeze. RDP (0): Protocol state changed to: ProtocolDisconnected(8) ![]() RDP (0): Protocol state changed to: ProtocolDisconnecting(7) RDP (0): Protocol state changed to: ProtocolActive(5) RDP (0): Protocol state changed to: ProtocolInactive(4) RDP (0): Protocol state changed to: ProtocolConnectingRDP(3) RDP (0): Protocol state changed to: ProtocolNegotiatingCredentials(2) RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1) RDP (0): Resolved '' to 'YY.YY.YY.YY' using NameResolveMethod_DNS(1) (This is with the exact same connection in the MSRDP client - just with and without a previous connection However, when the connection actually occurs there are a few differences. Most of the log files look the same, enumerating interfaces, etc. Still no luck locating a 8.0.16 that we could redistribute to affected customers. Once the first client's connection closes the other client will immediately be able to create a connection, but once again, will block all others.Ĭonnections from previous versions seem to be unaffected - only connections from 8.0.17 seem to be affected by this bug.Īlthough we normally use a connection broker to perform load balancing, we recreated the bug by using direct server connections as well, so it seems to be something with the RD Gateway / 8.0.17 Client itself. Other clients will not be successful until the first client's connection closes. Subsequent connections from the same client will not be successful until the first connection is closed. It does not appear to affect our 2008R2 RD Gateway infrastructure, only our 2012R2-based infrastructure.įurthermore, it appears that the 2012R2 RD Gateway will allow for a single 8.0.17 Mac client to create a single connection.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |