User guide

Another scenario, shown in Figure 4.4, is when the corporate site also uses a NAT device to
save IP addresses (double-NAT). Since the DSView 3 software client is trying to access a
private resource inside the corporate site, the TCP/IP ports used for HTTPS and the proxy server
must be configured to be exposed on the corporate NAT device.
Figure 4.4: Double-NAT Configuration (Client and Corporate)
Table 4.7: Double-NAT Configuration (Client and Corporate) Descriptions
Number Description Number Description
1 DSView 3 Software Client 7 NAT Device
2 Private 8 Private
3 NAT Device 9 DSView 3 Software Server
4 Client 10 Managed Appliance
5 Public 11 Corporate
6 VPN
NOTE: NAT devices may not be connected between the DSView 3 server and any managed appliances.
Licenses
License keys permit the operation of the DSView 3 management software on the hub server.
They also specify the number of managed devices that may be controlled by the software and
spoke servers allowed on a system. Managed devices include physical servers, routers, switches,
firewalls, blade chassis, hypervisor managers, hypervisor servers, virtual machines and any other
target device that can be managed by the DSView 3 software. If a managed device is available
through multiple connection methods, the managed device requires only one license as long as
it is merged into a single connection in the DSView 3 software.
Licenses may also be required to enable additional features. See Table 4.8 for more information.
60 DSView® 3 Software Installer/User Guide