Data Expedition, Inc. ®

Move Data Faster


Tech Notes
Configuring Firewalls
Vista Firewall
License Binding
Anon. Win32 servedat
Windows 7 Firewall
Amazon Web Services
NAS Authentication

Amazon Web Services

Tech Note History
Sep082014Clarify Private IP
Oct302013EC2 Update
Nov302012Irix Correction
Mar232011AWS EC2
Jan112011Virtual Machines
Nov302009Clarified IP binding
Sep082009Clarified migration process
Oct272008Add AIX Host ID
Jul252008Clarified private addresses policy
May212007First Post

MTP/IP License Binding

Most MTP/IP applications are licensed on a per-server basis.  The licensing terms generally require that each MTP/IP server license be bound to a specific network host.  The host may be specified using either a fixed IP address or a host identifier.

Customers must choose which methods best suit their deployment needs and provide the necessary information for each server license at the time of purchase.

Fixed IP Address

You may choose almost any static, unicast IP address.  The bound MTP/IP license will work with any host for which that address is assigned to the primary network interface card (NIC).  This allows you to completely change the host hardware, without disruption to your MTP/IP license.

The IP address you provide for binding must be on an active network interface of the system that is actually running the MTP/IP software.  Do not use the address of a router, virtual host, or other device.  Under Windows, you can see a list of available addresses by running the console command "ipconfig /all".  On all other systems, type the shell command "ifconfig -a" from an administrative or root account.

If the system is behind an NAT gateway or firewall, you must use a static, private address.  If a static IP address cannot be used, then you may need to use the host identifier instead.

Private network addresses which are commonly used for routers or subnets, such as or, are not permitted.

Host Identifier

The MTP/IP license may be bound to the host identifier of a machine.  The IP address may change, but the software will only run on that specific hardware.  If you acquire new hardware, the software will not run unless you update it as described below.

For Windows, Linux, Mac OS X, and FreeBSD, the host identifier is the MAC/Ethernet address of the host's primary network interface.  This interface must be available and active when the MTP/IP software is run.

For Solaris, HP-UX, and AIX, the host identifier is the value returned by the system "hostid" command.

For Irix, please supply the complete output of the command "sysinfo -vv".

Amazon Web Services EC2

Traditional host identifiers and IP addresses are not persistent in EC2 and cannot be used for MTP license binding.  Instead, you may bind to an Instance ID or Elastic IP address.  Make sure to discuss EC2 details with your DEI representative prior to submitting binding information.  See Tech Note 0025 for more about using MTP/IP software with Amazon Web Services.

Virtual Machines

License binding within virtual machines is permitted using Fixed IP Addresses as described above.  Binding within a virtual machine using a Host Identifier may be permitted, provided that the identifier is reasonably unique.


During the term of an active support contract for a given host license, you may make occasional changes to the IP address or host identifier to which the software is bound.  This may be done a reasonable number times to facilitate changes in your network infrastructure or evolving business needs.  It is not permitted as a substitute for acquiring multiple host licenses where needed.

Updating the license binding will require that you download new software executables from your customer website, and that you certify removal of the software from the old host.  You must have a current technical support contract to update your license bindings.  Contact your customer service representative or your local reseller to obtain a Host Migration request form.


Exceptions to these restrictions may apply.  Contact a DEI sales representative if you have unusual deployment needs that do not fit with the license binding described here.