IBM eServer iSeries Manual page 102

Local console connection problems
When setting up your local console you may encounter problems connecting. Failure to connect is
defined as problems resulting in the status not going to Connected and the emulator did not start. It is
possible that the status will go to Connected and the emulator starts but no console data is present. If
this is the case, see Troubleshoot emulator problems. Possible connection troubleshooting solutions
include:
Console fails to connect
Solutions to problems that occur when a local console fails to connect to an iSeries server.
Network connection errors
Solutions to problems that occur when a local console fails to connect to an iSeries server over a
network.
Error message: The connection to the system is not a secure connection
Solutions to problems that occur when a local console fails to make a secure connection.
Local or remote console status remains Connecting
Solutions to problems that prevent the local console from connecting to the server or prevent the
remote console from connecting to a local console due to improper hardware or software
configurations.
Console fails to connect
Solutions if your console fails to connect and your port detection fails.
Performance degradation on local console
Reasons for performance degradation when the communication port is not running a buffered
UART (Universal Asynchronous Receive/Transmit, serial port chip).
Unable to make a connection when infrared devices are installed
Solutions if the PC is having connection problems when using infrared devices.
Unexpected disconnects
Solutions if the PC, local or remote console, or both, have power management capabilities.
Use HyperTerminal to validate connectivity between client and the server
Solutions for using HyperTerminal for connecting to various sources.
Resynchronize the PC and service tools device ID password
Solutions for when the PC and the iSeries service tools device password do not match.
Console fails to connect: Under certain circumstances a directly attached console will fail to connect.
This may be the result of the server's communications adapter being deactivated for some reason, such as
an exception that took place. This most likely will appear during an IPL and may have an associated
system reference code (SRC) on the control panel along with the attention light. You can reset the
communications line by performing a function 65 followed by a function 66 on the control panel or
remote control panel. To reset the communications adapter, do the following:
To deactivate the communications line on the server, do the following:
1. If your system is not in manual mode, if the extended functions are not activated, or both, follow
these steps:
a. First, if your server uses a keystick, insert it in the key slot.
b. Place the server into manual mode by using the system's control panel.
c. Using the Up and Down buttons, select function 25.
d. Press the Enter button.
96
iSeries: iSeries Access for Windows Operations Console