Update: This problem was in version 4.2 when Satellites were fairly new. Issues like this don't seem to happen any more with version 6 (as of 2016). We need to do some troubleshooting to divide the problem space and find the root cause. Since it's just one Satellite, it's probably not the Central Monitoring service (otherwise the other Satellites would likely exhibit the same problem). When the problem is happening, try to RDP into the Satellite server, and then on the Satellite server, open a browser to https://{central server}:{central port}/ Can you get to the Central Server via the browser? Assuming you can, the next thing to do would be to look in the Satellite's log files. By default it is at: C:\Program Files\PA Server Monitor\Logs\PA Server Monitor_Satellite_Log.txt Does it show a failed connection and a reason?

We need to do some troubleshooting to divide the problem space and find the root cause. Since it's just one Satellite, it's probably not the Central Monitoring service (otherwise the other Satellites would likely exhibit the same problem). When the problem is happening, try to RDP into the Satellite server, and then on the Satellite server, open a browser to https://{central server}:{central port}/ Can you get to the Central Server via the browser? Assuming you can, the next thing to do would be to look in the Satellite's log files. By default it is at: C:\Program Files\PA Server Monitor\Logs\PA Server Monitor_Satellite_Log.txt Does it show a failed connection and a reason?