Hello,
to add to the last mail: we found out that re-connection is normal
default behavior if the user resizes the browser window.
From the guacamole manual we will test what this parameter in the
connection settings does:
|resize-method|
The method to use to update the RDP server when the width or height
of the client display changes. This parameter is optional. If this
value is not specified, no action will be taken when the client
display changes size.
Normally, the display size of an RDP session is constant and can
only be changed when initially connecting. As of RDP 8.1, the
“Display Update” channel can be used to request that the server
change the display size. For older RDP servers, the only option is
to disconnect and reconnect with the new size.
Possible values are:
display-update
Uses the “Display Update” channel added with RDP 8.1 to signal
the server when the client display size has changed.
reconnect
Automatically disconnects the RDP session when the client
display size has changed, and reconnects with the new size.
Regards,
Massimiliano Ballerini
On 27/09/2024 13:30, Massimiliano Ballerini wrote:
Hello,
I have some infos on the clients home situation from the helpdesk.
They have:
- Windows 10
- Google Chrome Version 128.0.6613.137 (official build) (64 bit)
- home connection type: xDSL FTTC (should be > 50MBit/s download)
- CPU: intel i5
- RAM: 8GB
The users are also reporting that resizing the browser window trigger
a reconnection. Is that wanted/normal?
Today i found in the catalina.out many lines like this:
ERROR o.a.g.w.GuacamoleWebSocketTunnelEndpoint - Connection to guacd
terminated abnormally: Connection to guacd timed out.
Could this be correlated with disconnections or it's normal?
From the guacamole server monitoring it has:
* max 12%CPU during the day
* max 30% ram used
* max 10 user connected at the same time
So I don't see why guacd should refuse connections from tomcat. I can
give full log or increase verbosity of the logs if could help with
analisys.
Regards,
Massimiliano
Il 27/09/24 09:13, Massimiliano Ballerini ha scritto:
Hello,
Thanks for the answer.
yes, I'm quite sure it's the home ISP connection the problem. It
looks like guacamole frontend "restarts" the browser connection in
the new version if it feels the user network is bad or unstable. I
guess it's in the javascript part. Some screenshot in attachment
1) every user has a different workstation in the office, if I connect
to their workstation I have no problems
2) I'll ask the helpdesk and see if there is something in common .
3) Yes, interface is kinda different, but nothing else changed in the
infrastructure.
Regards,
Massimiliano Ballerini
Il 26/09/24 22:39, Ivanmarcus ha scritto:
Massimiliano,
In the past when I've had these sorts of issues the problem has
turned out to be either with the external user's ISP, or something
internal to their location. In the latter case this has included the
user's children re-configuring the home network, or in some other
way interfering with the Guacamole traffic.
Although it may have happened directly after your upgrade the
scenario you've given suggests it's not likely to be your
installation, given you have ~48 other users that have no issues.
However here's some suggestions for troubleshooting:
(1) Do the users always connect to the same workstation? If so,
could you have them connect to a different workstation (that others
connect to with no problem), just to see if it made any difference?
From what you've said I wouldn't expect it to, however it could be a
worthwhile check.
(2) Is there anything different about these two users'
machines/browsers compared to those users that have no issue?
(3) That's quite an upgrade, did you do anything else on your system
and do you have a proxy involved? What do your logs say for the
problem users?
On 27/09/24 02:28, Massimiliano Ballerini wrote:
Hello,
we recently updated our guacamole server from version 0.9 to 1.5.5
and we are having an issue with some few users.
Our architecture permits users at home to connect to their PC in
the office with RDP. So the diagram is something like this:
user --> home ISP --> work ISP --> firewall --> guacamole server
--> PC
2 of around 50 users seems to experience frequent disconnections
web- side: the browser lose connection during the RDP session and
then "reloads" the page, reconnecting to the PC, but then the RDP
greetings/ disclaimer page pops up and the user has to click ok and
wait for Windows reconnection. After that the user is connected
again for a brief period.
Our helpdesk technicians could not reproduce the problem since they
connected to the same PCs and did not experience any disconnection.
We managed then to reproduce a similar problem generating a lot of
traffic on the connection used to reach the guacamole server.
We think the home Internet connection of these 2 users is slow or
low quality, and that is what is causing the malfunction, but that
wasn't happening with the previous version of guacamole.
I searched online for a solution or even a timeout parameter i
could increase to help these 2 users, but I'm finding only people
having problems with connection:
guacamole guacd server <--> PC with RDP
and not
USER <--> guacamole web server (the one with tomcat to be clear).
I'm having problem with the latter. Has any of you experienced
something similar?
Regards,
Massimiliano
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@guacamole.apache.org
For additional commands, e-mail: user-h...@guacamole.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail:user-unsubscr...@guacamole.apache.org
For additional commands, e-mail:user-h...@guacamole.apache.org
--
Massimiliano Ballerini
Laboratori Guglielmo Marconi
Via Porrettana, 123 - 40037 Pontecchio Marconi (BO)
e-mail:massimiliano.baller...@labs.it
web:http://www.labs.it
mob: +39 349 2600513
--
Massimiliano Ballerini
Laboratori Guglielmo Marconi
Via Porrettana, 123 - 40037 Pontecchio Marconi (BO)
e-mail:massimiliano.baller...@labs.it
web:http://www.labs.it
mob: +39 349 2600513
