Athar Company, User (Posts: 4)
Aug 06, 2020 7:27:18 am EDT
Conrad Sallian, Support (Posts: 2937)
Aug 06, 2020 1:26:32 pm EDT
Thomas Inman, User (Posts: 4)
Sep 18, 2020 12:25:51 am EDT
Pauline, Support (Posts: 2619)
Sep 18, 2020 5:45:49 pm EDT
Thomas Inman, User (Posts: 4)
Sep 18, 2020 7:54:13 pm EDT
Pauline, Support (Posts: 2619)
Sep 21, 2020 4:40:27 pm EDT
Thomas Inman, User (Posts: 4)
Sep 22, 2020 7:02:22 am EDT
Pauline, Support (Posts: 2619)
Sep 22, 2020 5:11:04 pm EDT
Please note that Direct connection can be only used in case if the remote Host machine can be addressed by its external IP address or hostname (DNS name). However, you can also establish a Direct connection over the Internet if you create a port forwarding rule in the router settings on the Host side. Please see this page for more information.Choosing Direct connection over Internet-ID does not work because some machines cannot be found by their name, and their IP addresses can change from time to time.
Please note that when using the RDP connection mode over the Internet, the RDP-over-ID feature is used automatically. In addition, please note that the RDP mode in Remote Utilities just launches the native Microsoft Remote Desktop Connection client from within Remote Utilities and connects to a remote computer using the standard RDP protocol.Using Internet-ID seemed like the most desirable method, but again, the connection status in the Viewer seems to change every time I look at it. It just keeps changing status, machines going offline and online again - unresponsive to launching a windows RDP session.
MaxBlitzer, User (Posts: 66)
Sep 29, 2020 12:39:04 am EDT
1. You can ONLY use Internet-ID feature as replacement for Hamachi in your case. Forget Direct Connection, forget RDP connection, especially if you want the person in front of the computer to see what you're doing on the screen instead of a login page like they would with RDP. Just right click on a host and "Full Control".Polina Krasnoborceva wrote:
Since I don't need any additional software to make direct RDP connections to local machines, my main interest is in connecting to remote machines not on my LAN. I have read those documents multiple times thinking I must have missed some detail, but I don't think that is the case. Choosing Direct connection over Internet-ID does not work because some machines cannot be found by their name, and their IP addresses can change fr om time to time. Using Internet-ID seemed like the most desirable method, but again, the connection status in the Viewer seems to change every time I look at it. It just keeps changing status, machines going offline and online again - unresponsive to launching a windows RDP session. Some machines display notification that the host software needs to be upd ated, in spite of already updating them both via the console and the Viewer. Viewer and Host installations are all beta2 version. Server is installed on an AWS VM, which appears to work.
While I work on making Remote Utilities work properly, the best alternative I've found and am using with remarkable success, is L0gmein Hamachi VPN (not installed on same machine as Viewer) to machines on a trusted remote LAN, and simply connecting to them via RDP. No tools, like screen recording and session notes, but it's super fast, spans multiple monitors, handles remote printing without need to install drivers or any additional configuration, and it rarely fails to connect. The only thing I really want fr om RDP is shadowing so I can see the console with full control, together with the user, to troubleshoot issues. So far, all of the information I've found after extensive searching appears to be obsolete for the most recent versions of windows 10 pro in 2020. I have used various command line flags, group policies, registry edits, and none of them worked across the Hamachi VPN to another remote LAN. RDP sessions with switches or without, the connection is a tcp session, not the console. So that was a lot of reading and testing to donate. I've also put in a lot of time trying to make RU work as designed.
* Website time zone: America/New_York (UTC -4)