Connection settings when the name of the higher system cannot be resolved

In an environment that uses host names as ID keys for operations, if the connection to the DNS server is interrupted for some reason (for example, because the system is a quarantined system), the client might no longer be able to resolve the name of a connection-target higher system. In such a situation, the client can resolve the name from the IP address in the communications protocol when it receives execution request information from the connection-target higher system. If the environment is such that it prevents the client from using this method to resolve the name of the connection-target higher system, the client can still poll for jobs and send inventory information to the higher system. During this time, the client will recognize the higher system that originates the execution request as the connection target.

To use this function, the following settings must be specified during client setup:

On the Default Running Status/Polling page, select the Client starts automatically at system boot check box.
On the Communication page, select the Connect to the upper-level system by using the IP address received via the startup request protocol check box.

When this function is enabled, a file for higher system addresses is automatically created on the client when it receives an execution request from a higher system. This file contains a mapping of the IP addresses and host names of the higher systems. Subsequently, the client uses the information in this file to perform name resolution and connect to the higher system.

Normally, there is no need to edit the file for higher system addresses. However, in an environment in which the name of the higher system cannot be resolved, you will need to create the file before you initially install a host name-keyed client.

For details about the settings to use when initially installing a host-name keyed client in an environment in which the name of the higher system cannot be resolved, see (1) Settings to use when initially installing a client in an environment in which the name of the higher system cannot be resolved. For details about the syntax required in the file for higher system addresses, see (2) Syntax in the file for higher system addresses.

Notes

You do not need to specify these settings when the IP address is used as the ID key for operations.
For higher systems of version 06-71 and earlier, the connection cannot be established correctly even if these check boxes are selected.
If the higher system is a cluster system, the connection might not be established correctly.
If the communication protocol of the execution request information is UDP in an environment in which the higher system uses multiple network adapters, the connection might not be established correctly.

Organization of this subsection: (1) Settings to use when initially installing a client in an environment in which the name of the higher system cannot be resolved; (2) Syntax in the file for higher system addresses

(1) Settings to use when initially installing a client in an environment in which the name of the higher system cannot be resolved

If you initially install a host name-keyed client in an environment in which the name of the higher system cannot be resolved, the client will not be recognized as a target because it cannot connect to a higher system. In such a case, create a file for higher system addresses beforehand, and use one of the following methods to save the file at the client.

Save the file for higher system addresses at the client after the client is installed.
After you have installed the client, save the file in the following folder:
```
JP1/Software-Distribution-installation-directory\MASTER\DB
```
Use the JP1/Software Distribution Administrator Kit to copy the file for higher system addresses.
Use the file copying function of the JP1/Software Distribution Administrator Kit. To do this, specify the following settings on the Copying Files page of the Create or Edit Installation Set dialog box while creating the installation set:

Setting Specification

Copy file File for higher system addresses you created

To directory %NETMDMP%\MASTER\DB

Setting	Specification
Copy file	File for higher system addresses you created
To directory	%NETMDMP%\MASTER\DB

When you restart the client after setup has been completed, the client will connect to the higher system based on the information in the file for higher system addresses.

(2) Syntax in the file for higher system addresses

The file for higher system addresses contains mappings for multiple connection targets. The client connects to the higher systems by means of the IP addresses corresponding to the host names as described in this file.

The following shows the syntax in the file for higher system addresses:

File name: SERVERIP.ini

Format

[host-name]
IPaddress=IP-address
[#-filecheck]
key=Programcheck

Description

host-name: Specifies the host name of a connection target for the client. This specification is not case sensitive. If the same host name is specified more than once, the first specification is used.

IP-address: Specifies the IP address that is to be associated with the host whose name is specified.

Multiple combinations of a host name and an IP address can be specified in the file.

Example

The following shows an example of a file for higher system addresses:

[host001]
IPaddress=10.100.100.20
[host005]
IPaddress=10.100.100.15
[host007]
IPaddress=10.100.100.57
[#-filecheck]
key=Programcheck

Note the following points when creating a file for higher system addresses:

If an IP address based connection error occurs, the erroneous host name and IP address combination are deleted.
If the #-filecheck line is removed, the file for higher system addresses is deleted.
Entries in the file for higher system addresses must consist of alphanumeric characters.
If the client is running Windows 98 or Windows Me, specifying a space or tab character within the brackets enclosing a host name will cause the host name to be recognized as invalid, resulting in an error.

All Rights Reserved. Copyright (C) 2009, 2013, Hitachi, Ltd.
Copyright, patent, trademark, and other intellectual property rights related to the "TMEng.dll" file are owned exclusively by Trend Micro Incorporated.

6.5.6 Connection settings when the name of the higher system cannot be resolved

(1) Settings to use when initially installing a client in an environment in which the name of the higher system cannot be resolved

(2) Syntax in the file for higher system addresses