Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE

Can SilkMeter be configured for clients machines on different subnets utilizing NAT?

Can SilkMeter be configured for clients machines on different subnets utilizing NAT?

SilkMeter can be configured as a license server for machines which see the server differently in the same network. Take for example the setup below:

This consists of one network but with two distinct subnets (remote clients for example could be overseas). Within the subnet which hosts the license server, the client machines can resolve the NAME of the server but not the NAT address. The opposite is true of the remote clients, they can resolve the NAT address but not the NAME.

An issue will arise when remote clients try to connect as the SilkMeter service will respond with the IP address of its first NIC in the IOR (in the above example This works fine for clients in the same subnet as they can resolve the server internal IP address however remote clients will report the error "The communication with the license server failed".

To work around this we need to configure the server to respond with its name and then update the HOST file on the remote client machines to resolve this name to the servers NAT address. This way both internal and remote clients get a response with the servers NAME. Internal clients recognize this instantly while the remote clients will resolve the name to the NAT address via the HOST file.

To configure the SilkMeter server to respond with its name add a entry to its config.xml file in C:\Program Files\Borland\SilkMeter\bin. This should be done with a text editor.

Using the above example would result in a config.xml like this:


and an entry in each client machine HOST file of:
192.xxx.xxx.xx anyserver1

If issues remain after implementing this approach please contact Technical support.

Old KB# 25193


Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Top Contributors
Version history
Revision #:
1 of 1
Last update:
‎2013-02-15 19:53
Updated by:
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.