Proxies are used to make discovery in network zones where the main vScope might not have full access on all relevant ports, such as a DMZ, a customer network or another closed network. vScope proxies communicate with the main vScope over one single port.
You can use as many proxies as you wish.
Prepare a server (in the closed network zone) where the discovery proxy shall run
- Dedicate a server in the network zone where the discovery proxy is intended to run
- You can run vScope discovery proxy on a dedicated server or locate the proxy on an already existing server located in the intended zone
- Windows OS*
- 6 GB RAM (Dedicate 4GB to vScope)
- 2 CPU Cores
- 60 GB HDD
- Java 64-bit (the installer will point to this java download site if not installed)
- Server needs to have internet connection
- NO additional database is required.
*vScope can run on Linux OS too, but the Linux-version only supports discovery of Windows systems through Win-RM (not WMI)
Install the proxy
- Download the proxy installer package from vScope.net – Latest proxy onto the intended discovery proxy server
- Run the installer
- Point the Host address (and IP-number or a DNS resolvable address) towards the the master vScope
- Specify a communication port between the proxy and the master. The default port is TCP 4445, but you can select any port of your choice.*
- Finish installer and let the proxy start
- The proxy will now identify itself with the master automatically (it might take a few minutes)
* Port 4445 actually only needs to be open from Proxy to Master. It is the proxy that initiates the communication to the master. What “Open” really means is that one TCP connection is allowed on any port from the proxy to the port 4445 on the master.
Notice that any discovery settings such as dynamic threading or RAM settings on the master vScope are not automatically distributed to the proxy installation. These settings are configured on the proxy in the same way as on the master vScope:
Locate the proxy in the Discovery Manager
- Open vScope and log in
- Go to the Discovery Manager and select the Proxies-tab
- You should now see the proxy being listed
- If you wish, you can rename your proxy to a friendly name, such as “DMZ”, “Area 51”, or “Customer zone”
- On this page you can also temporarily disable proxies and see the status of them
Note – Proxy does not show up in vScope
Ensure that ports are not blocked on either side (eg. Windows Defender).
Assign a target or target range to a proxy
- In this final step, you instruct the proxy where to run discovery.
- When a target, or target range, is assigned to a proxy, vScope will delegate the discovery of that target to the proxy
- The proxy will use the credentials specified for the selected target an for any other target