From user-return-4864-archive-asf-public=cust-asf.ponee.io@guacamole.apache.org Tue Dec 18 16:22:48 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 4824C180669 for ; Tue, 18 Dec 2018 16:22:48 +0100 (CET) Received: (qmail 41711 invoked by uid 500); 18 Dec 2018 15:22:47 -0000 Mailing-List: contact user-help@guacamole.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@guacamole.apache.org Delivered-To: mailing list user@guacamole.apache.org Received: (qmail 41701 invoked by uid 99); 18 Dec 2018 15:22:47 -0000 Received: from mail-relay.apache.org (HELO mailrelay1-lw-us.apache.org) (207.244.88.152) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Dec 2018 15:22:47 +0000 Received: from mail-ed1-f41.google.com (mail-ed1-f41.google.com [209.85.208.41]) by mailrelay1-lw-us.apache.org (ASF Mail Server at mailrelay1-lw-us.apache.org) with ESMTPSA id 9B7861066 for ; Tue, 18 Dec 2018 15:22:46 +0000 (UTC) Received: by mail-ed1-f41.google.com with SMTP id y56so14170216edd.11 for ; Tue, 18 Dec 2018 07:22:46 -0800 (PST) X-Gm-Message-State: AA+aEWYr2ZePHVRnN5oOsF1Ki5soxpcQ5sq6LL9yPy5Buh6je4ESeb3N dwBsWamKP2+GCvxhZH9hU3Zat2hkrjRhkJT2X1I= X-Google-Smtp-Source: AFSGD/XkeFOv8/YD1GOEX9lFffZrJ7RvIJ6XrrT3+aPOC52yBR4rrLfHNX+2lqkl6ROu5XnUrcEAFlWfkVn60mxc8Z0= X-Received: by 2002:a50:aa31:: with SMTP id o46mr16534982edc.23.1545146565671; Tue, 18 Dec 2018 07:22:45 -0800 (PST) MIME-Version: 1.0 References: <1545140748857-0.post@n4.nabble.com> <1545142910992-0.post@n4.nabble.com> In-Reply-To: <1545142910992-0.post@n4.nabble.com> From: Nick Couchman Date: Tue, 18 Dec 2018 10:22:34 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Built-in reflector/repeater support in guacd daemon (Guacamole protocol) To: user@guacamole.apache.org Content-Type: multipart/alternative; boundary="0000000000002c423c057d4d78fd" --0000000000002c423c057d4d78fd Content-Type: text/plain; charset="UTF-8" On Tue, Dec 18, 2018 at 9:22 AM sapphireimsuat 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 --0000000000002c423c057d4d78fd Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
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 tw= o
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 s= ome misunderstanding, here, about how Guacamole works.=C2=A0 Guacamole is d= esigned specifically for this type of scenario, and is designed to do it wi= thout any software other than a web browser on the client system.=C2=A0 The= Guacamole Server (guacd) does the translation between the Guacamole Client= and the remote desktop instances.=C2=A0 Guacamole Client does not get inst= alled on the roaming client machines, it gets installed on a Tomcat server = that then translates between HTTP(S) and the Guacamole Protocol, communicat= ing with guacd.=C2=A0 This actually works very well for the situation you m= ention, because you can set up that Guacamole Client system in a central lo= cation and have it facilitate the connections to the remote clients.
<= div>
Hopefully this helps, let me know if you have any furthe= r questions.

-Nick
--0000000000002c423c057d4d78fd--