In some scenarios a Tunnel client server's hub.log may display communication errors with other Tunnel client server via port 48002 even though Tunneling is properly set and is successfully communicating with it's Tunnel server.
Example of error seeing in hub.log with loglevel 3.
sockConnect - connect to 188.8.131.52 48002 failed 10060 ihubrequest: SessionConnect failed: 184.108.40.206/48002 hub: hubup - send failed for /UIMDomain/OtherTunnelClientHubName (220.127.116.11:48002 communication error)
UIM with Hubs that have "Enable Tunneling" configured.
Hubs trying to learn about other hubs in UIM
1. Stop the hub robot services on the systems included in the communication error 2. Set the broadcast_on value to no in the X:\Nimsoft\hub\hub.cfg file Example: broadcast_on=no 3. Reset the Hub's X:\Nimsoft\hub\hub.sds file Delete the X:\Nimsoft\hub\hub.sds file 4. Start the hub robot services 5. Confirm that the hub.log no longer shows the communication error