I am using the latest version of both the viewer/host and server 184.108.40.206 / 220.127.116.11.
I have host that constantly drop and reconnect over and over again. I have done a constant ping from the host in question to two locations at the same, not once does it come up with a bad pig or skipped ping. Perfect the whole time. Also only 1 of the multiple hosts on the same connection will drop and reconnect at any one time! I have 2 hosts at the same site, when I get one to stop bouncing the other starts bouncing and the one stops.
I also have noticed that IF the site has dropped and reconnected it will still show online on the Viewer, then when you click on it, it will go offline and then back online.
Let me know what logs you would like posted and I will post them.
Currently, we are working on a 64-bit server version and it is already available for testing. I recommend that you replace your current server with a 64-bit version and test to see if you still have issues. Here is how:
1. Back up your server installation folder - just copy it elsewhere
It is still happening, also it seems to only happens at sites that I have multiple host behind the same router. Its almost like the routing is not working right. Like its getting confused on what one its suppose to be talking too! So one constantly bounces! The patch has seem to fix my single host bouncing issues.
We are not sure what might be causing this, apart from possible routing/network issues on the Hosts' side. Do you have a system administrator on those site/sites who could check connectivity with your server and figure out the bounces?
I am the system admin, One system is using a dd-wrt router, and the other is using a netgear default. 2 host behind both routers. Only one host will bounce at any one time, never both of them If site 1 has Host 1 bouncing Host 2 never bounces. If you log into host 2 it will disconnect you, then host 1 will start bouncing constantly.
I also put a host on 2 more of my local LAN computers for a total of 3, and only 2 of them drop constantly at the same time. And that is local to the host and server on the same network.
And for even more testing, I changed each one to its own port, and same result.