Remote Connection Alternative
Hi, I need a Remote connection alternative. We use Logmein, Teamviewer, Splashtop. Does anyone know secure but less expensive one for Servers and workstations? One of my clients wants to change to something else.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Hi there,
depending on the OS you want to connect, there are also other solutions, like
VNC (transfer insecure, should only be used in LAN or via VPN)
AnyDesk (commercial like Teamviewer)
RemoteAdmin (same as above)
Spice (very similar to VNC)
SSH (as mentioned by others; ideal for *nix based systems, tricky on Windows)
...
depending on the OS you want to connect, there are also other solutions, like
VNC (transfer insecure, should only be used in LAN or via VPN)
AnyDesk (commercial like Teamviewer)
RemoteAdmin (same as above)
Spice (very similar to VNC)
SSH (as mentioned by others; ideal for *nix based systems, tricky on Windows)
...
If you are using Windows 10, you can use Quick Assist. (Included with Win 10) https://www.petri.com/how-to-use-windows-10-quick-assist-to-give-or-receive-remote-support
ASKER
Yea getting SSH to work might be an issue, We have 6 servers and many many workstations.
One thing I like with Logmein is 2nd factor auth
One thing I like with Logmein is 2nd factor auth
With a decent infrastructure like that, it should not be too difficult.
You could just tunnel RDP through SSH if you want.
LogMeIn is going via a third party, so your security risks are completely different than sticking with SSH (or any solution that does not rely on an external party). If implementing MFA is something you are wanting to do, then I would suggest doing that across the entire network, so that you need it to log in to a workstation or server, whether that is at the console, via RDP internally, or via RDP over SSH.
Hope that helps,
Alan.
You could just tunnel RDP through SSH if you want.
LogMeIn is going via a third party, so your security risks are completely different than sticking with SSH (or any solution that does not rely on an external party). If implementing MFA is something you are wanting to do, then I would suggest doing that across the entire network, so that you need it to log in to a workstation or server, whether that is at the console, via RDP internally, or via RDP over SSH.
Hope that helps,
Alan.
The only ugly part is getting sshd (server part of ssh) running on Windows.
Use https://winscp.net/eng/doc