guacamole-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nick Couchman <vn...@apache.org>
Subject Re: Built-in reflector/repeater support in guacd daemon (Guacamole protocol)
Date Tue, 18 Dec 2018 15:22:34 GMT
On Tue, Dec 18, 2018 at 9:22 AM sapphireimsuat <sapphireimsuat@gmail.com>
wrote:

> Hi Nick,
>
> Thanks for your suggestion. My understanding on your approach is, having
> two
> guacacd instance between two different network and allow connection.
>
> My query about roaming users is, assuming I have 100 end users and they are
> roaming in different locations and connecting to internet via broadband
> connection. All will have the client component and they should be able to
> connect to Guacamole server in a single port (where repeater is running).
> Connection will be initiated from roaming user-1 and reach repeater.
> Technician-1 will also be connecting to repeater to make connection with
> roaming user-1.
>

So, maybe there's some misunderstanding, here, about how Guacamole works.
Guacamole is designed specifically for this type of scenario, and is
designed to do it without any software other than a web browser on the
client system.  The Guacamole Server (guacd) does the translation between
the Guacamole Client and the remote desktop instances.  Guacamole Client
does not get installed on the roaming client machines, it gets installed on
a Tomcat server that then translates between HTTP(S) and the Guacamole
Protocol, communicating with guacd.  This actually works very well for the
situation you mention, because you can set up that Guacamole Client system
in a central location and have it facilitate the connections to the remote
clients.

Hopefully this helps, let me know if you have any further questions.

-Nick

Mime
View raw message