Hi Antony, I agree it could be that, however, it does not explain (in my mind) why would the Guacamole server behave differently when the user is from Europe or from Australia if the target is still in Australia. Is there any special connection happening from the end user all the way to the target somehow?
Additionally, can that 15 seconds timeout be increased somehow? Bogdan > On 14 Jun 2022, at 22:10, Antony Awaida <[email protected]> wrote: > > HI There: > > It may be a problem with the network latency. Have your user in Australia > check his latency to Europe/Azure using this: > > https://www.azurespeed.com/Azure/Latency > <https://www.azurespeed.com/Azure/Latency> > > Cheers, > Antony Awaida > CEO > www.apporto.com <http://www.apporto.com/> > > 2 min intro video Apporto for Business: > Apporto for Business — Introduction - YouTube > <https://www.youtube.com/watch?v=lyncxPtgncQ> > > 2 min intro video Apporto for Education: > https://www.youtube.com/watch?v=dUBk_cF3tY8 > <https://www.youtube.com/watch?v=dUBk_cF3tY8> > > > > > On Tue, Jun 14, 2022 at 12:07 PM Stefan Bogdan Cimpeanu <[email protected] > <mailto:[email protected]>> wrote: > Hello all, > I have this interesting behaviour,, that I can’t fully understand, maybe > someone can help out please. > > I have Guacamole deployed in several Azure locations in Europe. > I have servers again in Azure deployed in most of the regions. > > If I, from Europe, want to access via Guacamole, a server in Australia, it > all works ok. > If someone from Australia wants to access a server from Australia, via an > European Guacamole, they get a connection timeout: > > <Screenshot 2022-06-14 at 22.06.08.png> > > I understand round trips etc, but I really don’t see why would Guacamole > “care” where the user comes from. As long as Guacamole can access the target > server, I should get a connection, right? > Slow, but it should be there. > > Can anyone help figure this out? > > Regards, > Bogdan
