Celso Henrique

Hello people, I figured out that the problem is not the time, but incomplete connections. My application has a timer that runs indefinitely until get the connection with the Server. Some machines start the connection negotiation but it never ends because of local firewall rules. When this happens, the Manager stops to respond other connections (new or old) just trying to make this connection. Look the Wiresharck log attached. The IP 10.106.1.8 is the Server and the IP 10.106.22.95 is the Client. I would like to know how I can avoid this. Is there a way to identify these machines without use Wireshark? Is there a way to make Manager not stop to respond other machines? Thanks! BR.