This is a major problem for our staff who use home computers to connect with our servers. If I remove the KB (which simply installed RDC 8.1) and revert back to RDC 7.1 all works fine again. Client does not acknowledge the new destination and just barfs out an error about the server not working. The broker gives the client the new destination RDS server and disconnects. The initial connection is made to the broker. Win 7 圆4 with KB2830477 installed - cannot be load balanced by the broker I'm experiencing the very same symptoms but with different software: But I know the client can reach the server because if I don't trust the server certificate I get an SSL error. Otherwise it doesn't seem to log anything.
![download rdp client 81 download rdp client 81](https://blog.globalcloudsolutions.org/assets/ec13b.png)
If NTLM is on on the server, the server logs some stuff in TerminalServices-Gateway log. RDP ClientActiveX has been disconnected (Reason= 516) The multi-transport connection has been disconnected.
#DOWNLOAD RDP CLIENT 81 CODE#
RDPClient_TCP: An error was encountered when transitioning from TcpStateConnectingTransport to TcpStateDisconnected in response to 2 (error code 0x80004004). RDP ClientActiveX is trying to connect to the server (servername) Microsoft-Windows-TerminalServices-RDPClient/Operational In my case this is what happens in the logs on the client: I believe that wiping the profile off the machine would resolve it, but that is a bit drastic. another local Win8 user works, using the same TS username). Strangely a different user on the same machine works fine, so there mustīe something wrong on the client (i.e. This post has made me realise that it probably happened after the upgrade, and this was a machine that I was previously using with no issues.
#DOWNLOAD RDP CLIENT 81 WINDOWS#
Has anyone else come across this issue with the Windows 8. I could be wrong with that assumption but that seems to be the only explanation for it that I have seen while investigating it for the last few days. Used first when it attempting the redirection and hence I don't have the issue when connecting externally
![download rdp client 81 download rdp client 81](https://4.bp.blogspot.com/-B32M8142xDQ/Ve9GtJVKKuI/AAAAAAAAOcY/jhPf3BGLrNM/s1600/Chrome%2BRemote%2BDesktop%2Bon%2BNexus%2B7.png)
It seems to be that the new version of the RDP client () doesn't handle multiple IP address when redirecting while the older one does and because the public IP address is the smaller number that is the one that gets When I connectĮxternally the redirection works. I only have this issue when connection from the LAN. Both IP address are set to be sent when doing the relocation and here is where I thing the issue it. NowĮach Session Host has 2 NICs (an internal private LAN NIC and one with a Public IP Address). If I happen to land on the session server with the least amount of users it works but if I happen to need to be redirected to another server I get the generic 'Remote Desktop can't connect to the remote computer' error. We have a common DNS name for all 3 RD Session Our RD Infrastructure is setup with 3 x RD Session Hosts and 1 x Sesison Broker.
#DOWNLOAD RDP CLIENT 81 UPDATE#
Ever since I ran the update for 8.1 my Surface is not able to remote desktop to our Terminal Servers using Session Broker.