java.net.NoRouteToHostException: No route to host: connect error?To find technotes that describe known problems, go to the Host On-Demand support page at the following URL and click the technotes link:
http://www.ibm.com/software/webservers/hostondemand/support.html
If you are running Netscape 7.x browsers and the IBM Win32 1.4.0 JRE, you will be prompted to download a plug-in when you attempt to connect. To avoid this, upgrade your to V1.4.1.
When using the HTML-based or Combined models, the Host On-Demand client defaults to prompting for a Host On-Demand user ID and password if the Deployment Wizard files are not received from the Web server, or if they are not received in the expected format.
java.net.NoRouteToHostException: No route to host: connect error?
When Microsoft IPv6 Developer Edition is installed on Windows XP, all Host On-Demand Java applets fail with a
java.net.NoRouteToHostException: No route to host: connect error. This happens even if the protocol is disabled.
To fix this problem, try one of the following:
If you cannot enter user IDs and passwords on the login panel of the Host On-Demand client, try either using the IBM JRE version 1.3 plug-in, (or a new version of the plug-in), or clicking out of the field and onto the desktop and then back into the field.
When logging on to FTP sessions, the cursor may not appear in the user ID field and you may not be able to tab to it using the keyboard. If this happens, try upgrading to a later JRE.
You may see a security warning with the following error message when installing the Host On-Demand cached client using Internet Explorer:
An error occurred while accessing the online revocation server.
This error message occurs when the Certificate Revocation option in Internet Explorer is selected. You will be unable to connect to the server to verify that the certificate has not been revoked. To prevent this message, disable the option by selecting Internet Options > Advanced > Security and unchecking "Check for Publisher's Certificate Revocation".
When there are 20 or more defined sessions, sometimes the Host On-Demand desktop may appear very slowly. The problem might be caused by the the amount of time it takes to process the large number of defined sessions. To prevent the delay using the HTML-based model, try the following steps:
If you are not able to type your password when launching the Host On-Demand desktop from a Mozilla-based Netscape browser, try upgrading your JRE to a later version.
When using the cached client on OS/2 with Netscape Communicator V4.61, you must wait for the download complete prompt before restarting the browser. It may take a few minutes for you to receive the prompt, however, this allows the cached client to finish any updates completely.
If you are using Windows Terminal Server and/or have a low display resolution, a NullPointerException may be thrown by the class file WVolatileImage, which can be seen in the Java Console. When this happens, users are not presented with their configured sessions. You can avoid this by setting a higher display resolution or by using the IBM 1.4 plug-in. If the HTML page has been created for the configuration server-based model, you can avoid this by adding the parameter <PARAM NAME=Bookmarking VALUE=false>.
If you receive the following error when using the User Profile Manager on Netscape browsers while loading the Locally installed client from the Start menu,
Cannot find the file C:\hostondemand\HOD_en.html (or one of its components). Make sure the path and file name are correct and that all required libraries are available.click OK and the Locally installed client will load in the browser.
Logging on and off any of the Host On-Demand clients repeatedly without restarting the Netscape browser first can cause the browser to remove files from cache that are needed in order for the clients to function properly. The browser removes files in order to reduce the cache. Restart your browser after logging off and before logging on to any Host On-Demand clients while using Netscape to prevent problems with the clients.
You can start a maximum of 10 to 12 Host On-Demand sessions in this environment.
When using a Host On-Demand session, you can save session configuration changes, such as screen size and colors, in the following two ways:
HODRemove.html to remove the Cached client.
If your SSH FTP or VT session fails to start and you receive a java.lang.IllegalStateException: zip file closed
, try upgrading your JRE. You may also try disabling the
caching function of the Java plug-in's Control Panel.
If the IME keypad overlaps a Host On-Demand session window, you may get incorrect results when you click the mouse in the keypad.
With Netscape 4.x on a Linux client, you may not be able to resize the Administration window when you are configuring Host On-Demand. If you resize the Administration window, you may either be logged off the Host On-Demand server, or you will see the following message in the browser:
Your browser does not have JavaScript support or the support is not enabled.Try upgrading your browser.
When you reload a session by refreshing the browser screen or using Action > Refresh in Netscape 6, you will find the following exceptions in the Java Console. You can ignore the exceptions.
Exception occurred during event dispatching:
java.lang.NullPointerException: null pData
at sun.awt.windows.WInputMethod.handleNativeIMEEvent(Native Method) at sun.awt.windows.WInputMethod.dispatchEvent(Unknown Source) at sun.awt.im.InputContext.dispatchEvent(Unknown Source) at sun.awt.im.InputMethodContext.dispatchEvent(Unknown Source) at java.awt.Component.dispatchEventImpl(Unknown Source) at java.awt.Container.dispatchEventImpl(Unknown Source) at java.awt.Component.dispatchEvent(Unknown Source) at java.awt.EventQueue.dispatchEvent(Unknown Source) at java.awt.EventDispatchThread.pumpOneEvent(Unknown Source) at java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.awt.EventDispatchThread.run(Unknown Source)
During the installation of WebSphere Studio Application Developer - Integrated Edition (WSAD-IE) (formerly VisualAge(R) for Java), WSAD-IE sets the global environment's CLASSPATH to include the Host On-Demand J2EE connector. This connector has a version of the Host On-Demand code that is common to the Host On-Demand clients. In Netscape 4.x and Internet Explorer 5.x, the browser always loads Java classes from the system CLASSPATH before the network. This means that when WSAD-IE is installed, the browser loads some classes from the connector before loading the correct version of the class from the network.
During WSAD-IE installation, the Windows CLASSPATH is updated to include the following directories:
x:\IBM Connectors\class x:\IBMVJava\eab\runtime30
These directories contain .jar files with classes that conflict with Host On-Demand classes. Most users do not need these directories in the classpath because they are used only for Java applications that use WSAD-IE's Host On-Demand connectors.
If Host On-Demand does not work after you install WSAD-IE, try the following workarounds:
Host On-Demand V7, V8, and V9 with Internet Explorer and Java 1 support sharing of the cached client between users on a Windows multi-user machine. In Host On-Demand V8 and V9, this support also works for browsers that support a Java 2 plug-in.
In addition, you can use the SharedCachedDirectory HTML parameter to specify a shared cached client install directory. However, do not specify a directory that contains DBCS characters. DBCS characters in shared cached client directories are not supported and will not designate the cached client as shared. Use single Latin-1 characters instead.
Using the cached administration client with Start Session enabled, you may encounter a grey screen when clicking on the Users/Groups task. If this occurs, try upgrading your Java 2 plug-in to the latest service level.
Use Telnet or Netstat to determine if a port is accessible. Do the following:
Netstat -a at a command line to see if the ports are active. If not,
refer to your operating system documentation for information regarding activating ports.NCoDServices.RAS.txt,
located in the \private directory. telnet and click OK.If you need to call the IBM Host On-Demand Support team, you can provide them a trace to help determine the cause of your problem. To learn more, click here.
