You have now made sure that the agent has the required information about the Frontend server. Now you should verify the agent's connection to the PerformanceGuard Frontend server and the onward connection to the Backend server:

Telnet to Frontend Server

Use Telnet to connect to the PerformanceGuard Frontend server:

On the computer that has the agent installed, select /Start, type cmd and press ENTER to open a command prompt.
At the command prompt, type the following and then press ENTER:

telnet <IP address of frontend server> 4001

Port 4001 on which the frontend server listens for data from agents. If your organization uses a different port number for this purpose, you should of course use that port number.

3. Type p within a few seconds after the screen clears, and before the connection is closed. You should now see the version number of the PerformanceGuard frontend server.

Example: PerformanceGuard Frontend Server 6-6-27151-ff66c-11212 build.start=08/04/15-10:58:31 - Ping reply

This proves that the Frontend server is able to receive data from the agent.

What if I don't see the version number?

In that case there is a problem with the Frontend server connection. See Troubleshoot Frontend Server Connection in the following.

What if I do see the version number, but the command prompt also says "Connection to host lost"?

Don't worry, that's just because the telnet session has ended after you got the required information.

Troubleshoot Frontend Server Connection

This is only required if you had problems connecting to the Frontend server from the computer that has the agent installed.

You should verify if a network problem or firewall prevents the computer that has the agent installed from connecting to the Frontend server. You can do this by repeating the telnet test on the computer that runs the Frontend server:

On the computer that runs the Frontend server, select /Start, type cmd and press ENTER to open a command prompt.
At the command prompt, type the following and then press ENTER:

telnet localhost 4001

3. Type p within a few seconds after the screen clears, and before the connection is closed. You should now see the version number of the PerformanceGuard frontend server.

Example: PerformanceGuard Frontend Server 6-6-27151-ff66c-11212 build.start=08/04/15-10:58:31 - Ping reply

This proves that the Frontend server is running.

- If you can connect to the Frontend server locally, but not from the computer that runs the agent, there is very likely a firewall blocking port 4001 at some point between the agent and the Frontend server. Note that Windows Updates may automatically install firewalls.
- If you can't connect to the Frontend server locally, do the following:
  - Select /Start, type services.msc and press ENTER. Then verify that the PerformanceGuard Frontend Server service is started.
  - Open [PerformanceGuard installation folder]\collector\conf\config.properties and verify that value of the Port parameter is 4001. If another port number is used, try the telnet tests with that port number. If the tests are successful, the agent should use that port number.
  - Check the Frontend server log file at [PerformanceGuard installation folder]\collector\logs\. Search for error messages. Also search for the agent ID of the agent that has the problem. You may be able to find a specific error message related to that agent.

Telnet to Backend Server

Now connect to the PerformanceGuard Backend server from the computer that has the agent installed as well as from the computer that runs the Frontend server:

Select /Start, type cmd and press ENTER to open a command prompt.
At the command prompt, type the following and then press ENTER:

telnet <IP address of backend server> 4008

The default listening port is 4008.

3. Type p within a few seconds after the screen clears, and before the connection is closed. You should now see the version number of the PerformanceGuard Backend server.

Example: PerformanceGuard Backend Server 6-6-27151-ff66c-11212 - Ping reply

This proves that it's possible to communicate with the Backend server.

- If you can't connect to the Backend server, do the following on the computer that runs the Backend server:
  - Select /Start, type services.msc and press ENTER. Then verify that the PerformanceGuard Backend Server service is started.
  - Open [PerformanceGuard installation folder]\notification\conf\config.properties and verify that value of the backend.port parameter is 4008. If another port number is used, try the telnet tests with that port number. If the tests are successful, the frontend should use that port number: On the computer that runs the frontend server, open [PerformanceGuard installation folder]\collector\conf\config.properties and change the value of the backend.port parameter.
  - On the computer that runs the Backend server, open the Backend server log file at \[PerformanceGuard installation folder]\notification\logs\ and search for error messages.

Search this documentation

On this page

In this section

Browser not supported