Skip to content
vScope Support Page

Discovery Proxies

Discovery proxies are essential for performing network discoveries in restricted zones where the main vScope instance may not have direct access, such as a DMZ, customer networks, or other closed network environments. Proxies communicate with the main vScope over a single port, allowing you to manage multiple network segments efficiently.

Preparing the Proxy Server

  • Select a Server: Choose a server in the network zone where the proxy will operate. This server can be a dedicated machine or an existing server within the network.

System Requirements

  • OS: Windows OS*
  • RAM: 6 GB (dedicate 4 GB to vScope)
  • Storage: 10 GB HDD
  • CPU: 2 cores
  • Database: Not required

*vScope can also run on Linux, but the Linux version only supports the discovery of Windows systems via WinRM (not WMI).

Installing the Proxy

Windows

  1. Download the Installer: Access the installation package on the server where the proxy will be installed.

  2. Run the Installer:

    • During installation, point the Host Address to the main vScope (either by IP address or DNS).
    • Specify a communication port between the proxy and the main vScope (default is TCP 4445, but any open port can be used).
    • Complete the installation and start the proxy.

Note: Proxy configurations like dynamic threading and memory allocation need to be set manually on each proxy.

Linux

  1. Download the Proxy Installer Package:

  2. Run the Installer and configure the connection to the master vScope:

    • Edit the file /etc/vscopeproxy/config.ini.
    • Add the row: proxy.master.host=vscope-master, where “vscope-master” is the hostname or IP of the vScope Master.
    • If you have changed the port, add: proxy.master.port=4445. Replace 4445 with the port you are using.

  3. Save the config.ini file and restart the service.

Registering the Proxy in vScope

  1. Open vScope and Log In.
  2. Navigate to Discovery > Proxies > Available and click Refresh if the proxy does not appear immediately.
  3. Approve the Proxy: Select the proxy and approve it to establish the connection.
  4. Connect the Proxy:
    • In the Approved tab, click Refresh to connect the proxy.
    • You can rename the proxy or assign it to specific target(s) or target range(s). To edit, click the proxy entry, make changes, and click Save.
  1. Manage or Remove Proxies:
    • To disable or delete a proxy, untoggle or remove it in the Discovery Manager.
    • If the proxy remains installed, it will reappear under Available upon deletion.

Troubleshooting Proxy Issues

Missing Data from Proxy Scans

1. Verify Proxy Setup in Discovery Manager

  • Confirm the proxy appears in Discovery Manager with a green status indicator. This confirms it is successfully connected to the main vScope.

2. Proxy Not Showing?

  • Ensure the proxy is configured to connect to the correct IP address and port of the main vScope.
  • Re-run the proxy installer if necessary.

3. Building a Troubleshooting Table

To confirm whether the proxy scanned the network, create a troubleshooting table in vScope:

  1. Select IP addresses as asset type.
  2. Apply a filter that matches IPs in the target network (e.g., 192.168.100.*).

The resulting table will show all IPs found by the proxy and the method used to find them.

No IPs Found…

If the table is empty, vScope may not have located any assets on the proxy network. Verify that the proxy is assigned to the correct targets in Discovery Manager.

IPs Found Only by Raw Ping

If IPs are listed as found only by Raw Ping, this indicates that vScope couldn’t inventory them further due to credential or firewall issues.

  1. Ensure the correct credentials are added in Discovery Manager.
  2. If the problem persists, check the debug log on the proxy server:
Terminal window
C:\vScopeProxyData\log\debug.log

Frequently Asked Questions

How Are Proxies Updated?

Proxies are automatically updated when initiated by the main vScope server. If a proxy hasn’t been updated, manually download and reinstall the proxy agent.

Proxy Does Not Appear in vScope

If the proxy doesn’t show up in vScope, verify that the necessary ports are open and not blocked by firewalls (e.g., Windows Defender).

Does the Skip List Apply to Proxy Scanning?

Yes, the Skip List applies to both master and proxy scans, blocking excluded ranges or targets from discovery.

Can Multiple Proxies Be Used Simultaneously?

Yes, vScope supports multiple proxies. Each proxy can be assigned to specific targets or target ranges in Discovery Manager, allowing you to manage and scan multiple network zones efficiently.

How Do Proxies Handle Credentials?

Proxies rely on the credentials configured in the main vScope instance. Ensure that credentials for the target resources are correctly added to the Discovery Manager and assigned to the appropriate targets.

What Happens If a Proxy Connection Fails?

If a proxy loses its connection to the main vScope, it will pause its activities until the connection is restored. Ensure that the network between the proxy and the main vScope is stable and that firewalls are not blocking communication on the configured port.

Can Proxies Perform Independent Scans?

No, proxies operate under the control of the main vScope. They rely on the main vScope instance to initiate scans and receive configuration updates.

Is It Possible to Limit the Scope of Proxy Scanning?

Yes, you can assign proxies to specific targets or target ranges in Discovery Manager. This ensures that the proxy only scans resources within its designated scope.

How Do Proxies Communicate With the Master vScope?

Proxies communicate with the master vScope over a single TCP port (default is 4445). Ensure that this port is open and accessible between the proxy server and the main vScope server.