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

Step 2: Selecting an SQL Server

In this step, the wizard allows you to either select an existing SQL server instance for use with NetResident or create a New SQL server:


If you create a new SQL server, you should specify a new server name, which must be unique for the given computer. After that, the wizard will automatically download Microsoft SQL Server 2014 SP2 Express or Microsoft SQL Server 2016 SP1 Express from Microsoft’s official Web site (an Internet connection is required) and then install it. Once the installation has been completed, a new SQL server instance will appear on the list of available servers.

If you decide to use an existing SQL server, select one of the server instances listed in the wizard window. You may want to click Refresh to update the list of servers to display all running server instances on your LAN and the local host. Once you have selected an existing SQL server, click Next to have the NetResident Database Manager connect to the selected SQL server. If the connection attempt fails, you will see the following dialog:


Typically, this might happen when trying to connect to an SQL server that was not installed by the NetResident Database Manager, in which case you should enter the correct SQL server login and password. You should contact the server administrator to get the credentials or try to use the default “sa” account; see this document if you encounter a problem.