Remote Console Connection Problems; Remote Console Through Dial-Up Fails To Connect To Local Console; Local Console Name Mismatch When Remote Console Connects To The Local Console; Troubleshooting Authentication Problems - IBM System i Manual

Connecting operations console
Hide thumbs Also See for System i:
Table of Contents

Advertisement

"Installing HyperTerminal" on page 102
To install HyperTerminal, follow these steps.

Remote console connection problems

When setting up your remote console, you might encounter problems connecting. Possible
troubleshooting solutions include these topics.

Remote console through dial-up fails to connect to local console:

Here are the solutions to a problem that occurs when a remote console modem fails to establish a
connection with a local console.
While you are connecting a remote console to a local console, you may encounter remote console
connection problems. These are solutions to a problem that occurs when a remote console modem fails to
establish a connection with a local console:
v If your PC modem is listed as a Standard Modem option in the Modems folder, configure it with a
different manufacturer and model.
v If you have an original equipment manufacturer (OEM) modem, your OEM modem may not be
configured correctly. If that is the case, try to configure it using some similar modem setups.

Local console name mismatch when remote console connects to the local console:

Here are some reasons for a possible console name mismatch when the remote console connects to the
local console.
It is important that the user at both ends check the Local Console column in the Operations Console
window. The names must be the same.
What TCP/IP uses for a name is retrieved and placed there. When the remote console is then configured,
make sure the name of the local console is the same. It is possible to have two different system names on
the same PC. The name used for Operations Console is taken from the DNS entry in the TCP/IP service.

Troubleshooting authentication problems

When setting up your initial connection, you might encounter authentication problems.

Authentication errors

While you are connecting a local console to a system, you may encounter local console connection
problems. These are solutions to errors that occur when Operations Console cannot complete a
connection between a system and a local console (PC). The errors consist of software configuration
problems or unrecognizable service tool user IDs.
Tip: Verify that you are entering a valid service tools user ID and password during the configuration
wizard.
You might also receive an error message regarding a secure connection.
Related reference
"Error message: The connection to the system is not a secure connection" on page 100
You may receive this error message: The connection to the system is not a secure connection.

Troubleshooting emulator problems

When setting up your initial connection you may encounter emulator problems.
If the emulator window did not start and the connection status is not Connected, refer to the Local
console connection problems topic.
104
System i: Connecting to System i Operations Console

Advertisement

Table of Contents
loading

Table of Contents