GUACD server and RDP server are in the same network. Only one of the user faced this issue out of 80.
*PING STATUS from GUACD server :-* [root@guacd-server]# ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=54 time=32.3 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=54 time=32.4 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=54 time=32.3 ms 64 bytes from 8.8.8.8: icmp_seq=4 ttl=54 time=32.3 ms 64 bytes from 8.8.8.8: icmp_seq=5 ttl=54 time=32.4 ms 64 bytes from 8.8.8.8: icmp_seq=6 ttl=54 time=32.2 ms 64 bytes from 8.8.8.8: icmp_seq=7 ttl=54 time=32.4 ms 64 bytes from 8.8.8.8: icmp_seq=8 ttl=54 time=32.2 ms 64 bytes from 8.8.8.8: icmp_seq=9 ttl=54 time=32.1 ms 64 bytes from 8.8.8.8: icmp_seq=10 ttl=54 time=32.2 ms 64 bytes from 8.8.8.8: icmp_seq=11 ttl=54 time=32.4 ms 64 bytes from 8.8.8.8: icmp_seq=12 ttl=54 time=32.5 ms 64 bytes from 8.8.8.8: icmp_seq=13 ttl=54 time=32.4 ms 64 bytes from 8.8.8.8: icmp_seq=14 ttl=54 time=32.4 ms 64 bytes from 8.8.8.8: icmp_seq=15 ttl=54 time=32.4 ms *PING STATUS of RDP server from GUACD server :-* [root@ guacd-server]# ping 10.1.1.138 PING 10.1.1.138 (10.1.1.138) 56(84) bytes of data. 64 bytes from 10.1.1.138: icmp_seq=1 ttl=128 time=0.338 ms 64 bytes from 10.1.1.138: icmp_seq=2 ttl=128 time=0.304 ms 64 bytes from 10.1.1.138: icmp_seq=3 ttl=128 time=0.285 ms 64 bytes from 10.1.1.138: icmp_seq=4 ttl=128 time=0.291 ms 64 bytes from 10.1.1.138: icmp_seq=5 ttl=128 time=0.276 ms 64 bytes from 10.1.1.138: icmp_seq=6 ttl=128 time=0.314 ms 64 bytes from 10.1.1.138: icmp_seq=7 ttl=128 time=0.292 ms 64 bytes from 10.1.1.138: icmp_seq=8 ttl=128 time=0.320 ms 64 bytes from 10.1.1.138: icmp_seq=9 ttl=128 time=0.313 ms 64 bytes from 10.1.1.138: icmp_seq=10 ttl=128 time=0.266 ms 64 bytes from 10.1.1.138: icmp_seq=11 ttl=128 time=0.294 ms 64 bytes from 10.1.1.138: icmp_seq=12 ttl=128 time=0.256 ms On Tue, Jul 23, 2019 at 9:26 PM Nick Couchman <[email protected]> wrote: > On Tue, Jul 23, 2019 at 11:37 AM Amarjeet Singh <[email protected]> > wrote: > >> My guess is that the network you're working on is unstable enough that >>> you're losing data along the way. 150-200ms is a lot of latency >> >> Latency was 15ms at this moment. >> >> > Okay, but the point is, the errors you're getting don't really indicate > that anything is going wrong on the Guacamole Side. I don't see any > messages about segfaults or abnormal termination by either guacd or > Tomcat/Guacamole Client. It would seem that something inside the network > is causing issues - either momentary latency problems, or packet loss, or > something along those lines. From the looks of the messages on the RDP > server, it would appear this is likely happening between guacd and the RDP > server, as it looks like the RDP server terminates the connection. > > We'll be happy to help if there are any further log messages that are > available, or anything you can find that indicates it's an issue specific > to Guacamole, but at this point it's hard to say (for me, anyway) what the > issue is without more direct ability to look at the systems and networks > involved. > > -Nick > >>
