As part of testing, we tried to reduce the threshold value for a sql query, but alert was not raised.
When you tried to open the hub GUI for the remote hub we noticed a windows communication issue randomly occurred.
Normally that indicates that there is a communication problem between the Primary<->Remote hub.
Check local machine firewalls and/or intermediate, and remote firewalls.
Check Windows events via event viewer (Application / System Log) for any crashes/errors/AV interference with any hub.exe processes
Make sure that the Primary hub-> Name Services has an entry for the remote hub.
Also check traceroute/tracert between those hubs.
And when you setup the ATTACH and GET queues, you should disable the nas replication and forwarding on the remote hub so its not redundant.
If the ATTACH and GET queues dont resolve the issue, please ensure you can do the following and let me know the results pass/fail:
telnet FROM the robot TO the remote hub on port 48002
telnet FROM the remote Hub TO the robot on port 48000
telnet FROM the remote hub TO the Primary hub on port 48002
telnet FROM the remote hub TO the Primary hub on port 48000
Check the local and remote firewalls on the robot and both hubs to ake sure all Nisoft Programs are allowed.
Add the Remote hub IP address to the hub Name Services via the Primary Hub GUI ad let me know if the Primary hub sees the remote hub.