How to redirect Hostname, Domain Name and IP/Port addresses (NetworkRedirection)

Save to PDF

Applies to: AppAcceleratorV 4.5.1810.22909

12/07/2019 Cliff Hobbs   ID: 344723

Overview

Cloudhouse Compatibility Containers™ provide network redirection through the NetworkRedirection Feature for Hostname, Domain Name, and IP /Ports. This allows client or server applications running in Containers to have their network requests redirected to new names, IP addresses or Ports, thus enabling you to migrate applications to new servers without changing an application's source code. 

Note

These features only apply to applications and processes running in a Container. The behaviour of other applications running on the server/desktop will not be affected.

Use Cases

  • Hostname virtualisation with <Network ThisComputer="old_machine_name"> is for server applications where you don't have the installation media, and the application has been extracted from the server it is running on. This feature can be used to virtualise the hostname of the server the application is running on so that it believes it is running on the original server.
  • Domain Name redirection with <DomainName> is for server applications where you don't have the installation media, and the application has been extracted from the server it is running on. This feature is used to redirect the name a client or server application expects to find on the network to one that is actually present on the network.
  • <Connect> enables applications to accept connections <From> one IP address or port <To> another. For example, if you need to run multiple instances of a desktop application that is configured to use a fixed port address preventing it from running on a server operating system (for example Citrix Virtual Apps (XenApp)).

Configuration Examples

Hostname Virtualisation

<AAV>
    <Features>
        <Feature>NetworkRedirection</Feature>
    </Features>

    <Network ThisComputer="SomeComputerName">
    </Network>
</AAV>

Domain Name Redirection

Given the following configuration, Containers will perform Domain Name redirection from the "oldmachine" to the "newmachine" first, then apply any "Connect" redirection.

<AAV>
    <Features>
        <Feature>NetworkRedirection</Feature>
    </Features>

    <Network>
        <DomainName>
            <From>oldmachine</From>
            <To>newmachine</To>
        </DomainName>
    </Network>
</AAV>

IP and Port Redirection

Redirect network connections <From> for example 192.168.2.1 on Port 13000 <To> 127.0.0.1 on Port 12000.

<AAV>
 <Connect>
    <From>
       <IP>192.168.2.1</IP>
       <Port>13000</Port>
    </From>
    <To>
       <IP>127.0.0.1</IP>
       <Port>12000</Port>
    </To>
  </Connect>
</AAV>

Logging

When the  <DomainName> feature is enabled, AppAcceleratorV will log:

"Server redirection from %old% to %new%"

when the configuration file is read.

Only Microsoft valid server names are supported. The following messages are logged if a server name does not meet Microsoft's naming conventions:

"Server name cannot begin with a period (.) and will not be virtualized"
"Server name cannot be longer than 15 characters and will not be virtualized."
"Server cannot contain invalid character "invalid_character" and will not be virtualized"

If <To> is not specified, the following message is logged:

"Server redirection will not redirect from %old%." 

If <From> is not specified, the following message is logged:

"Server redirection will not redirect to %new%."

Warning "HookWinsockHookAPIs" Deprecated

The Container will detect if "HookWinsockAPIs" is enabled and log "NetworkRedirection feature should be used instead."

Source:
Was this article helpful?

Table of Contents

    Can't find what you're looking for?

    Contact Support