Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Netflow Traffic Analyzer (NTA) > NTA - Knowledgebase Articles > Capture Netflow Traffic of a Endpoint through a Proxy Server

Capture Netflow Traffic of a Endpoint through a Proxy Server

Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 1,607 Votes: 0 Revisions: 9

Issue

Netflow Traffic Analyzer (NTA) fails to capture the flow information from an endpoint that is connected through a proxy server.

Environment

NTA

Cause

If an endpoint is connected through a proxy server, the destination IP address for the endpoint is actually the proxy server itself. The proxy server terminates the HTTP session with the endpoint, communicates out to the Internet, then feeds the result back to the enpoint. NTA sees only the flow between the proxy and Internet.

Resolution

  1. The proxy server configuration may be changed to an intercepting proxy also known as transparent proxy. Refer to the supplier documentation for proxy configuration.
  2. If the proxy configuration is successful, then the NTA is not aware of the proxy's existence and the source/destination IP address are not rewritten from the endpoint's perspective.
  3. Verify the full conversation details in NTA. 
Last modified

Tags

Classifications

Public