User`s guide

Release Notes
AA–RFBPE–TE 387372-005 Page 57
If hosts files are not exactly the same on all systems, the h_name returned may
vary on different Agent systems. For example,
xxx.xxx.xxx.xxx client.somewhere.com client
will return client.somewhere.com in the h_name field, but
xxx.xxx.xxx.xxx client client.somewhere.com
will return client in the h_name field.
In some situations, you can configure the way a system uses DNS and its local
hosts file. Please refer to your system documentation to find how your system is
configured. Some systems may be configured to do the following:
• Check its local hosts file first, then go to DNS.
• Go to DNS first, then check its local hosts file.
• Ignore DNS even if configured.
• Ignore the local hosts file.
The best way to verify what needs to be used for a Client name in the Client
authorization list is to write a program that runs on the agent system and prints
the h_name field returned by gethostbyaddr(<client IP address>). Remember the
dynamic IP address allocation is not supported.
Add New System by Using Internet Protocol Address Crashes
The SWCC Client may crash when you attempt to add a system by using the
agent system’s Internet protocol (IP) address rather than the agent system’s node
name. This occurs when the client system does not have a DNS server
configured that knows the agent system, and the agent system is not in the client
system’s hosts file. To correct this situation, add the agent system to the hosts
file on the client system.
If you receive an "Invalid host" or "Host not known" message when you attempt
to connect to an agent system, the solution is not to try the IP address. Fix your
DNS server configuration, or if that is correct, confirm the DNS server knows
the agent system. If you are not using DNS, make sure the agent system is in the
client system’s hosts file. Remember, WINS is not supported by SWCC.