With this feature, connections only need to be set up one time. What sets visionapp Remote Desktop 2010 R2 apart from some other tools is its ability to share connections between many desktops it can also save all connection information into a database so that many people in the department can reuse the connection.
If you ever identify a need for an additional protocol, visionapp Remote Desktop 2010 R2 can be extended to support that new service, too.
#VISIONAPP REMOTE DESKTOP ALTERNATIVE FREE#
Since this conglomeration, the open source mRemote is no longer under development all development activity is now focused squarely on the commercial visionapp Remote Desktop tool.Īvailable in free and pay editions, visionapp Remote Desktop 2010 R2 enables admins to connect to servers using these connection methods: RDP, ICA, VNC, SSH, HTTP, and Telnet. The current version of visionapp Remote Desktop was born through the combination of the open source tool mRemote and the then current version of visionapp Remote Desktop.
One tool I decided to learn more about is visionapp Remote Desktop 2010 R2. In response to my TechRepublic tutorial about Microsoft’s Remote Desktop Connection Manager, a number of members posted comments about which tool their organization uses for server administration. I believe updating the certificate the web server (gateway) uses will resolve my issue.The visionapp Remote Desktop 2010 R2 Setup Wizard One Difference I did notice between everything else that works (both internally and externally) and the only thing that doesn't work, connecting to Virtual Desktops externally, is the Remote Desktop Connection Box isn't quite the same.įor connections that do work the publisher is listed as "Unknown Publisher" while the connection that works, the publisher is listed as "". I have confirmed the correct certificate is installed on the WebServer from the RD Gateway Manager application. I definitely do see where the certificate being provided is the servers self generated certificate, not the trusted certificate I obtained online. The one that does not work, the gateway when connecting to Virtual Desktops is: Īfter creating a CName record through my DNS provider that points to am getting a new error message: Your computer can't connect to the remote computer because the Remote Desktop Gateway server address requestedĪnd the certificate subject name do not match.The one that works, the gateway when connecting to Physical Computers is:.I'm assuming the Physical Computers Connection references the Application Setting "DefaultTSGateway" I noticed the Gateway listed when connecting to Virtual Desktops was different than the Gateway listed when connecting to Physical Computers. Also I have performed the following actions referenced in the following URL without resolution:Īs a side note, if I just manually open Remote Desktop Connection from my external computer and type in the Computer field, I can connect to the Web Server without any problems.I have verified Forms Authentication is enabled.I have modified the Application Setting "DefaultTSGateway" within IIS under RDWeb -> Pages to match the url which points to my webserver (gateway server).I have generated a certificate from with the name which has been installed on the webserver (gateway server).I access RDWeb through a url, this gets redirected to.
The physical server fulfills this role instead. The web server is currently fulfills all of the Remote desktop roles, except for the Virtualization Host. To avoid issues with the router blocking traffic.
I have setup the other virtual server as a web server, which sits in a DMZ temporarily One of the virtual servers is the DC, it currently has No Remote Desktop Roles. In the protocol stream and the client was disconnected."Ĭurrently I have 3 servers, one physical server, 2 virtual servers. When attempting to connect to the Physical Computer, after entering my login credentials I receive the error "The logon attempt failed." On the server I see an associated error of "The RDP protocol component X.224 detected an error (0) See any associated evens listed in the event viewer of the server. When attempting to connect to the Virtual Desktop, after entering my login credentials I receive the error "Your computer can't connect to the remote computer because the Remote Desktop Gateway server is temporarily unavailable." I do not I receive a different error based on what feature of RDWeb I'm trying to use. Internally all of this works without a problem. I'm also trying to use RDWeb to remotely access a physical computer from the "Connect to a remote PC" section. I'm currently trying to use RDWeb to remotely access a virtual desktop from the "Remote Apps and Desktops" Section.