I use it myself to act as my gateway into my network. Instead of opening several ports for RDP/VNC/SSH to various machines (I used non-standard ports, so 3389 is not open), I instead have https access to guacamole on my webserver, and then from there I can connect to whichever systems I have enabled.
This provides me one way in to manage; I don't need multiple firewall rules, I don't have to maintain VPN, I don't need any software on the machine I'm connecting from: just a web browser. I also don't need outbound firewall rules from where I'm connecting from; https is already allowed (whereas my non-standard and even standard outbound ports at work are blocked). For myself, it eliminates the need for TeamViewer or other similar products. If you're still requiring connecting to a VPN, then yes, it is not accomplishing much for you besides ACLs and centralization. If all you're looking for is simpler management of remote connections only internally to your network, and maintaining VPN access, I'd recommend Devolutions' Remote Access Management. On Mon, Jan 13, 2020 at 8:41 AM WhiteTiger <whitetiger_it...@yahoo.it.invalid> wrote: > Forgive my perhaps too naive question, but I'm trying to understand. > If I have to connect to the Guacamole Server via VPN and the server is > located in the LAN, then, why should I use it to connect to PCs for example > with RDP? > If I am in the LAN, with the VPN, then I can already connect directly to > the > PCs via RDP without the need for an intermediate server. > I'm missing something, but what? > > > > -- > Sent from: > http://apache-guacamole-general-user-mailing-list.2363388.n4.nabble.com/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscr...@guacamole.apache.org > For additional commands, e-mail: user-h...@guacamole.apache.org > >
