You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@guacamole.apache.org by ma...@gmail.com on 2021/09/02 04:41:38 UTC

RE: THE NETWORK CONNECTION IS UNSTABLE

Thanks nick.

 

We are going through your suggestion on user side there is no lack of network issue I am also checking the firewall and switches. as per your last point I am disable the ping of that URL server but for checking the ping from user side we hit this ip which is on same network same ISP.  This “THE NETWORK CONNECTION IS UNSTABLE” message showing on that browser that time there is no any huge latency and no more delay on network , server also running fine with no lack of resources. 

 

So please guide us more how we can stable it.

 

From: Nick Couchman <vn...@apache.org> 
Sent: Wednesday, August 25, 2021 8:43 PM
To: user@guacamole.apache.org
Subject: Re: THE NETWORK CONNECTION IS UNSTABLE

 

On Wed, Aug 25, 2021 at 12:56 AM <manoj2patil@gmail.com <ma...@gmail.com> > wrote:

From many days we have facing THE NETWORK CONNECTION IS UNSTABLE regarding issue , As per checking this massage is showing even there is no any drops on the client side also in the trace root . We have daily showing this type of massage in the client side. i have shared ping and tracer root details for your reference so i request you to please  check this issue on priority and check this issue on the priority.....

 

There isn't much that the people on this list can do to check this issue for you. It's your environment, you're going to have to investigate the issues. We can provide pointers for what you should look at, but we can't solve this for you.

 

The items to check that could cause this are:

* Unstable network connectivity, where packets are getting dropped between the user's browser and the server running Tomcat (Guacamole Client). This is the most likely cause.

* High latency on the network connection between user's browser and the Tomcat server, where the packets are taking too long to travel between the user's browser and the Tomcat server.

* Lack of resources on the server running Tomcat (Guacamole Client), where the Tomcat process cannot respond to client requests in a timely fashion. Check the load and resource availability on this server, particularly CPU and memory, to make sure that it has the resources to process the connections that it is servicing.

* Lack of resources on the user's browser, where the browser cannot get adequate time to process the connection.

* There could be network equipment between the user and the Tomcat server that is delaying traffic, such as an Application or Deep Packet Inspection firewall.

 

It seems that you've possibly checked the first two, though I do not consider a ping and traceroute to be conclusive evidence that the network is operating correctly. It is good to verify that, for sure, but doesn't mean that the network is not interfering with some traffic (HTTP/HTTPS) and not other traffic (ICMP). Also, a couple of other points about your ping/traceroute pictures:

* The ping output you posted covers about 30 seconds of time. In that 30 seconds, at least one of the pings went from 15-16ms up to 100ms. It's impossible to tell from that screenshot you've provided whether that's a single occurrence in 1000 pings, or something that's more of a pattern, happening every 30 seconds, etc.

* You've provided absolutely no indication of what you're pinging and from where. You have a ping going to the IP address 103.115.232.19, but in the photo I also see a different URL to another IP. Since the network connection unstable message is indicative of connectivity issues between the user's browser and the system running Tomcat (Guacamole Client), I would expect to see a ping to the IP address where you're accessing Guacamole, from the end user client running the web browser.

 

-Nick