Specifications
From Windows:
addresses. When unresolvable names, WINS names or unqualified DHCP names are used, this
causes Java to throw an UnknownHostException.
This error message may also occur under the following conditions:
l Server name does not exist. Check for misspelled server name.
l Misconfigured DHCP servers may set the fully-qualified domain name of RMI servers to be
the domain name of the resolver domain instead of the domain in which the RMI server
actually resides. In this case, RMI clients outside the server's DHCP domain will be unable to
contact the serverbecause of the its incorrect domain name.
l The server is on a network that is configured to use Windows Internet Naming Service
(WINS). Hosts that are registered under WINS may not be reachable by hosts that rely solely
upon DNS.
l The RMI client and server reside on opposite sides of a firewall. If your RMI client lies outside
a firewall and the server resides inside of it, the client will not be able to make any remote calls
to the server.
When using the LifeKeeper GUI, the hostname supplied by the client must be resolvable from the
server and the hostname from the server must be resolvable by the client. The LifeKeeper GUI
catches this exception and alerts the user. If the client cannot resolve the server hostname, this
exception is caught and Message 115 is displayed. If the server cannot resolve the Client hostname,
this exception is caught and Message 116 is displayed. Both these messages include the part of the
Java exception which specifies the unqualified hostname that was attempted.
Included below are some procedures that may be used to test or verify that hostname resolution is
working correctly.
From Windows:
1. Verify communication with the Linux Server
From a DOS prompt, ping the target using the hostname:
ping <TARGET_NAME>
For Example:
ping homer
A reply listing the target's qualified hostname and IP address should be seen.
2. Verify proper configuration
l Check configuration of DNS or install a DNS server on your network.
l Check the settings for ControlPanel->Network->Protocols->TCP/IP. Verify with
your Network Administrator that these settings are correct.
Note that the hostname in the DNS tab should match the name used on
the local name server. This should also match the hostname specified in
the GUI error message.
SteelEye Protection Suite for Linux245