NetResident - Network Content Monitoring Tool

Prev Page Next Page
System Requirements
What Network Content NetResident Can Analyze
What’s New in NetResident 3.0
NetResident Architecture
Deploying the Application
Before You Begin: Network Visibility
Step 1: Deploying the NetResident Service and Console
Step 2: Deploying NetResident Agents
Ensuring Connectivity Between the System Components
Tips and Tricks
Setting Up the Database
Step 1: Creating a New Database and Configuration File
Step 2: Selecting an SQL Server
Step 3: Selecting a Database Location and Name
Step 4: Setting Database Access Token
Step 5: Summary
Working with NetResident
Understanding the Difference Between the Display and Capture Filters
Remote Connections
Adding Exceptions to NetResident Agents
Manual SQL Server Installation
Analyzing Imported Capture Files
Frequently Asked Questions
Sales and Support

Before You Begin: Network Visibility

The key to successful network monitoring is the visibility of network traffic. If you need to monitor only one computer on the network, there is no network visibility question: You can simply install and run NetResident on that computer. However, if you need to monitor multiple computers on a LAN, it is important that you understand how to achieve network visibility (i.e., the ability to “see” network traffic of other stations from a single observation point).

In brief, to monitor other computers on your LAN, you need to install NetResident on a gateway computer or use a switch with the “port mirroring” feature. There are many possible network layouts, so if you are new to network monitoring, we recommend that you read the detailed, illustrated white paper by TamoSoft, Promiscuous Monitoring in Ethernet and Wi-Fi Networks (a PDF version is also available.)