Following are some common problems that you may encounter when using Java Plug-in for Solaris. For additional information, consult the Java Plug-in FAQ.
Java Plug-in does not recognize Netscape Navigator settings -- Java Plug-in reads Navigator's settings when it starts. If you make any changes to Navigator settings, you must restart Navigator for Java Plug-in to recognize the new settings.
You cannot restart the Java Plug-in Console -- If you close Java Plug-in Console, you must close and then restart Netscape in order to restart the Console.
You encounter a web page containing a Java Plug-in applet that says you do not have the appropriate plug-in installed -- First, verify that you correctly set all environment variables. Then, make sure all MIME types are enabled by choosing About Plug-ins from the Help menu.
Cookies are not accessible when you use Java Plug-in with a protected server -- Most mechanisms used to enable protected directories on the web server use cookies. However, Java Plug-in does not provide cookie support. Although you can log in to your web server and generate a cookie with Navigator, the cookie is not accessible by Java Plug-in.
You experience problems when rendering an applet -- When an applet is loaded on a web page that specifies Java Plug-in, a SecurityException is triggered. In order to perform certain security checks, the Applet Security Manager must find the IP address from which your applet was downloaded. If your network does not support Domain Name Service (DNS), these security checks may fail. To correct this problem, specify an IP address rather than a host name in the URL when visiting the target web page.