Since the access logging is not available for the connection between client tools and remote servers, troubleshooting is not easy.

Actually, my Production servers are hosted by RWS CloudOps, and those multiple servers are load balanced.  And each of users worldwide are experiencing differently regarding ClientConfig sync and connection response time.  Possibly, connecting server is differentiating the experience.  However, according to RWS support, we don't have ways to identify which of load-balanced server client tools (i.e. Publication Manager, Authoring Bridge) are currently connecting to.

My suggestion is to let client tools to identify which remote server instance it is currently connecting to and then write that information to the client tool log file.  In addition, the remote server should log the client tools host names when it get ClientConfig file and other requests.  With that logging, we can easily identify which server the client tool is connecting to when it encounters intermittent issue.