Debugging Network Agent
- Article Number: 000001609
- Products: Forcepoint URL Filtering, Forcepoint Web Security, TRITON AP-WEB, Web Filter & Security, Web Security and Web Filter
- Version: 8.5, 8.4, 8.3, 8.2, 8.1, 8.0, 7.8, 7.7, 7.6, 7.5, 7.1, 7.0
- Last Published Date: September 27, 2018
Network Agent is not working properly. How do I enable debugging to troubleshoot the issue?
The options below are for gathering data for troubleshooting and can be done in any order. However, if going down the list, make sure to undo the Network Agent Packet Capture before performing the PrintSelf.
Note Debugging can cause Network Agent to slow down considerably. This setting is only recommended for troubleshooting Network Agent.
For more information on ConsoleClient, view the following articles:
A packet capture can show you what can be seen by the network card. Reset packets generated by Network Agent have the ip.id field of the packet set to 0x2f2.
Note Network Agent causes Wireshark to not function properly on open. To make a packet capture with Wireshark if Network Agent and Filtering Service are on the same server:
Examine ports and session states:
Once Network Agent has seen a packet and established communication with the Filtering Service, there should be 50 ports connecting Network Agent with Filtering Service.If any blocking has occurred, there will also be connections to port 15871 in the time-wait state.