This view shows the targets located at another site. The free PingView program must be used in conjunction with PVProxy to obtain this information.
The PVProxy utility accepts requests from ProbeView to perform pings and TCP probes in its network. In addition, PVProxy can communicate with a running copy of PingView. The "target set" of PingView is similar to that of ProbeView, but it can be much larger and may be organized into groups.
After you create a "PingView Server" target, refreshing it sends a request through its proxy to PingView, which replies with information about its last refresh. The individual targets referenced by the remote PingView are displayed in the "Subordinate Targets" page.
The status (success/failure) of a "PingView Server" target is really the status of the entire group of targets referenced by PingView. The targets that failed are indicated by a beige background in ProbeView.
In other words, you can view the status of an entire remote network using a single ProbeView target. The detailed (target by target) information is then available by touching the target's name in ProbeView's main page.
You only need one PVProxy to access the data from many running PingView instances. Each PingView instance can be configured act as a server, supplying its status information to PVProxy or other PingView instances upon request.
The communications between PVProxy and PingView are password-protected and encrypted. However, the communications between ProbeView and PVProxy are only protected by a password-- they are not encrypted.
However, it should be remembered that no vital data is transmitted between ProbeView and PVProxy. Only the names or addresses of targets are sent.
Future versions of ProbeView and PVProxy may include support for SSL or TLS, which would guarantee a secure connection.