How to capture service traffic

Netwrix Data Classification
Other
https://kb.netwrix.com/3531
Copy Article URL Copied

In more complex or secure environments there will sometimes be the need to debug connectivity between the Netwrix Data Classification services and an external HTTP connection (Website, SharePoint site collection etc). In these cases “Fiddler” is a free tool that can be used to exclude certain issues as well as debug the exact HTTP traffic that is occurring.

When Fiddler launches and attaches it adjusts the current user’s proxy settings to point at Fiddler, running on 127.0.0.1:8888 by default – however, this will not include the core services (Collector, Indexer and Classifier) which must be configured manually.

Should the failure case succeed when Fiddler is running (and configured) it would suggest that a proxy configuration is required within the environment that has not been configured correctly. We would suggest co-coordinating with your network team to confirm the exact requirements to connect between the server and desired destination.

Fiddler can be downloaded from the Telerik Website.

  1. Start Fiddler
  2. Launch Notepad with elevated permissions (Right Click program → Run as Administrator)
  3. Open the following file: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config\machine.config
  4. Add the below XML block as a peer to the existing system.net element, replacing any existing defaultProxy element if present
  5. Save the file
  6. Restart the core Services (CollectorIndexer and Classifier)

<!– The following section is to force use of Fiddler for all applications, including those running in service accounts –>
<system.net>
<defaultProxy
enabled = “true”
useDefaultCredentials = “true”>
<proxy autoDetect=”false” bypassonlocal=”false” proxyaddress=”http://127.0.0.1:8888” usesystemdefault=”false” />
</defaultProxy>
</system.net>

Go Up