Frequently Asked Questions
General QuestionsQ: What does the error "Failed to launch Shared Shell" mean?
A:
This means Java Web Start was unable to connect to the Shared Shell
server to download the application. The exact error message can usually
be found by clicking Details and checking the Wrapped Exception tab.
Error messages like "java.net.UnknkownHostException: sharedshell.sun.com" or "java.net.ConnectionException: Connection timed out: connect" usually indicate you need to set up a Proxy Server configuration for Java. By default Java Web Start will try to use your browser proxy settings, but in some cases you will need to configure it manually, depending on your platform:
Once the proxy configuration has completed, try re-loading the Shared Shell page and launching Shared Shell again. Note that if you are on a VPN connection that requires a proxy, then disconnect from the VPN, you will need to go into the Java (or Network) preferences and change these settings to work on a non-proxied Internet connection. If the Shared Shell server is down for any reason, the Details/Wrapped Exception page will typically show "...Connection refused" if the server is up but Shared Shell services are down, and a "... no response from server" message if the server is down. Your Sun Support Engineer can open a ticket for Shared Shell in either of these cases. It is also possible to get a "Failed to launch Shared Shell" message if you are trying to connect from an IP address in an Export-restricted country (Cuba, Iran, Libya, North Korea, Sudan, or Syria). Q: What user name and password do I use to log in to Shared Shell?
A:
If you are not a Sun employee, use the same sun.com login that you use on other Sun sites. Visit the "Join Now" link at http://portal.sun.com/ to register for a new account, or http://reg.sun.com/accounthelp if you need help with an existing account. For Sun employees, use your official employee email address and your employee (LDAP) password.
Q: I forgot my password or am having other problems logging in.
A:
Visit the registration "Need Help?" page at http://reg.sun.com/accounthelp to reset your password, look up your user name, or submit a request for help.
Q: How do I get a user name and password?
A:
Visit the Join Now link at http://portal.sun.com.
Q: When do I select the Use Proxy box?
A:
If your web browser requires the use of a proxy server to connect to the Internet, select this box. If you aren't sure if you need to use a proxy server, check with your network administrator. Everyone on the Sun internal network, SWAN, needs to check this box.
Q: What do I put in for the proxy settings?
A:
Your network administrator can can tell you these settings. You might also be able to determine these settings from your web browser:
If your web browser is set up to use an automatic proxy configuration URL, or to automatically detect settings, check with your network administrator. You need to know the SSL/HTTPS proxy server name and port, or SOCKS5 proxy server name and port. Use the Test button to check whether your settings are valid. Q: I got an "Unable to resolve Shared Shell server ..." error message. What does it mean?
A:
You are probably on a network that requires a proxy server to access the Internet. Please see the previous information about proxy servers.
Q: I got a "Failure communicating with Shared Shell Server ..." error message. What does it mean?
A:
You are either on a network that requires a proxy server or the Shared Shell server is suffering a temporary outage. Your Sun support engineer can help you verify this condition and can report the outage, if necessary.
Q: What should I do about the "Unexpected error starting session ... Connection refused" message?
A:
The target system is refusing your Telnet or SSH connection. If you chose Telnet, try switching to SSH, or vice versa. Shared Shell needs to make a direct connection from the initiator system to the target system using SSH or Telnet.
Q: What does the "The authenticity of host ... can't be established" warning mean?
A:
This is not an error message. You are being shown the SSH key fingerprint of the target system in order to verify the authenticity and security of the connection. This is a feature of the SSH protocol designed to protect against spoofing by showing you a fingerprint of the unique server key that you can match and verify. If verified, this ensures your username and password are not transmitted to a hostile server. The next dialog will prompt whether you want to create a "known_hosts" file in your Shared Shell directory so that you are only prompted for this key/fingerprint verification once per host.
Q: My target server requires SSH with RSA-key authentication. How do I use Shared Shell?
A:
Currently Shared Shell supports only SSH with password authentication.
You need to have Shared Shell connect to an intermediate host that has a full-featured SSH client, such as a development/test server that allows Telnet or SSH with password authentication. Q: Can I use Shared Shell to connect to the console port on my server?
A:
You can use Shared Shell in this way only if that console port is accessible through a terminal server or console server that allows access with Telnet or SSH. You need to specify the host name or IP address of the terminal server or console server and the corresponding port that will connect to the target machine.
Q: I get a Security Warning: "Warning: Failed to verify the authenticity of this certificate because there was an error parsing the certificate...." What's wrong?
A:
This generally happens when you have an old version of Java 1.4.2 installed on your system, possibly alongside a newer version of Java. Shared Shell uses a production Sun/Verisign certificate, but this root certificate and chain is only supported in Java 1.4.2_06 and newer. Note that this may be true even if you check our "Verify your Java installation" link and it shows an up-to-date version of Java. This is because the Sun installer for Java allows multiple versions of the SDK and Runtime to be installed at the same time.
The best solution is to remove older/unused versions of Java. On Windows, use Start -> Control Panel -> Add/Remove Programs and remove all but the most recent version of Java. On other platforms, this is typically configured through your PATH or environment settings. On Solaris, make sure your /usr/java symbolic link points to the most recent version of Java you have installed. Q: What terminal type should be used for Shared Shell?
A:
Shared Shell emulates a subset of the ANSI and VT100 terminal standard. You should set your "term" environment variable to "vt100" or "xterm."
(Note that some Sun products such as ILOM consoles use the "sun" terminal type by default. Change this to "vt100" or "xterm" for best results.)
Q: What are the known issues regarding Shared Shell?
A:
[CR 6535391] - Enabling "Assistive Technology Support" on Solaris/Gnome causes high CPU usage after running for several hours If "Assistive Technology Support" is enabled in the Solaris/Gnome environment, Shared Shell performance may degrade after running for several hours due to issues in the Java/Gnome accessibility infrastructure. If you require assistive/accessibility technology, you may need to exit Shared Shell and restart after running for more than 2-3 hours. Workaround: from the Gnome panel, click Launch -> Preferences -> Accessibility -> Assistive Technology Support. Un-check the "Enable assistive technologies" checkbox. Exit all open applications, then log out and log back in before launching Shared Shell. [CR 6680838] - Terminal size is fixed at 32x132. Currently, even if you resize the Shared Shell window, the terminal stays the same size. A fix for this is being prioritized. [CR 6498339] - Support Microsoft Proxy Servers that require NTLM authentication. A fix for this is being prioritized. A possible workaround (not tested, endorsed, or supported by Sun) is the open source "NTLM Authentication Proxy Server" project, at http://ntlmaps.sourceforge.net/. [CR 6693188] - {New 4.2 feature for Sun participants only.} At the end of the session, a terminal log window is displayed and the participant has the option to copy the text or save it to a file. A large log will take a few moments to transfer. Only the last 2 MB of the session log is available. [CR 6729513] - If an incorrect Sun Online Account user name and/or password is used to start Shared Shell, the error message will be: "TSX004 Timeout occurred waiting for Authentication response. Please try again in several seconds." If you have forgotten your password, please use http://portal.sun.com to reset it. If you continue to receive the TSX004 error and are using a correct user name and password, please inform your Sun Services Engineer about the problem and ask them to open a ticket for Shared Shell. Or, use the feedback form on http://sun.com/123.. [CR 6734099] - If 15 or more Shared Shell applications are launched from the same desktop, you may experience connection errors.. [CR-6806456] - The file transfer between the Initiator's target System and participant's system may not be successful If the FileXferBlockSize specified more than 4096 bytes. Workaround: Do not specify the FileXferBlockSize more than 4096 bytes in preferences editor.[CR 6684880] When using JRE version 1.5.0_03 and entering an invalid target host port/password, the Shared Shell client terminates instead of showing an error message. Workaround: Update the Java Runtime Environment (JRE) [CR 6850628] - Sun participants are presented a log of the terminal text and chat messages at the end of a session. The chat message log does not correctly display some multi-byte languages such as Japanese and Chinese. [CR 6850628] JRE 1.4 version does not support multi language chat input in Shared Shell. Workaround: Update the Java Runtime Environment (JRE) |
Future Proof the DatacenterWatch how Sun increased storage capacity by 244%, increased computer power by 456%, cut energy costs by 60% and were awarded $1.2 million in rebates...
| |||||
|
|
