# Agent Network Traffic Is Missing

> Fix missing network traffic measurements from one particular agent.

Source: https://docs.capaone.com/performanceguard/troubleshooting/troubleshoot-agent/agent-network-traffic-is-missing/  
Product: PerformanceGuard — a separate CapaSystems product; do not apply this page to any other.

<font style="color: #404040;">Symptom: In the PerformanceGuard web interface, you are not able to see any network traffic measurements from a particular PerformanceGuard agent.</font>

## **Possible Causes & Solutions**

:::caution
You can only do this if you're a PerformanceGuard administrator.
:::

- **Computer Isn't Online**

To check: Select **ANALYZE > Computers > Computer Search**, and search for the computer in question. In the search results, click the name of the computer. Then, in the **Computer Info** tab's **Agent Info** section, check the **Last Delivery** time, and match that with the **Delivery Interval**. If, for example, the agent on the computer is set to deliver data to PerformanceGuard every 180 seconds, and it hasn't done so, then the computer is in all likelihood not online.  
To fix: Further troubleshooting should focus on finding out why the computer isn't online.

- **WinPcap Driver Isn't Properly Initialized**

To check: Select **ANALYZE > Computers > Computer Search**, and search for the computer in question. In the search results, click the name of the computer. Then, in the **Computer Info** tab's **Agent Info** section, check the **Options**. For a correctly working agent there should be a line that says **Winpcap Driver OK**.

To fix: If there isn't a line that says **Winpcap Driver OK**, try selecting the **Message Log** tab to see if there are any log messages that explain the problem. If not, go to the computer that has the agent installed, open a browser and connect to *http://localhost:4007*. Then, in the agent information window that opens, select **View > Errors** and check if that detailed log of the agent's activity contains any log messages that explain the problem. Further troubleshooting should be done on the computer that has the agent installed. A restart of the computer may be required.

:::caution
4007 is the default port number. If the port number has been changed in your organization, PerformanceGuard administrators can view it in the PerformanceGuard web interface: Select **ADMINISTRATION > Agent Configuration > Configurations**, click the **Edit** link next to the agent configuration group that the agent belongs to, select the **Agent Configuration** tab, scroll down to **Agent Service Parameters** section and look for the **Web Server TCP port** number.
:::

- **Aggregate Job Isn't Running**

To check: Select **ADMINISTRATION > Status > System Status**, select the **Scheduled Jobs** tab, and verify that the **Traffic Data Aggregation** job is enabled and has the status OK.

To fix: A typical problem is that the SQL Server Agent isn't running. Select ![](/attachments/performanceguard/0da377f4-f7fe-4f07-9719-9f25c66679e0.png)/**Start**, type services.msc and press ENTER. Then make sure that the **SQL Server Agent** service is started.

- **Agent Monitors Wrong Adapter**

The PerformanceGuard agent only monitors network traffic going to and from a single network adapter. Many computers have more than one adapter, so the agent will choose the same adapter that it uses to connect to PerformanceGuard.

To check: On the computer that has the agent installed, open a browser and connect to *http://localhost:4007*. In the agent information window that opens, select **View > Adapters** to view a list of available adapters on the computer. Then select **View > Errors** to view a detailed log of the agent's activity (including non-errors) and search the **Name** column for *Opened adapter* to verify which adapter the agent currently monitors.

:::caution
Remember that the log lists the most recent messages at the bottom.
:::

To fix: If the adapter that the agent monitors isn't the one that you want the agent to monitor, you can force the agent to monitor a specific adapter. See, for example, the *MonitoredNicIP* [Agent Registry Keys](/performanceguard/technical-reference/agents/agent-registry-keys/) in the Technical Reference section of the help system. See, for example, the *MonitoredNicIP* agent registry key setting in the Technical Reference Manual.
