IBM eServer iSeries Manual page 104

v If you are running Windows NT on a local console directly attached to the server with remote access
allowed, check the following:
– Verify that the configuration of the modem that receives the call at the local console is not set to
Dial out only.
– Try to reinstall Microsoft Service Pack 6 (or later).
Console fails to connect and port detection fails: If your console fails to connect and your port
detection fails, here are some possible reasons:
v Sometimes RealPlayer or RealJukebox interferes with port detection and usage.
v Some PDA drivers or software may also prevent connections or port detection.
Performance degradation on local console: The most likely reason for performance degradation is that
the communication port is not running a buffered UART (Universal Asynchronous Receive/Transmit
serial port chip).
Go into the Advanced settings for the serial port and verify the check mark is checked to use a buffered
UART. Make sure the Receive Buffer setting is not set to the right-most setting.
If that does not help and you suspect that there is a possibility that the PC may truly not have the
buffered UART, IBM recommends that you slow the connection down between the PC and server.
Depending on the operating system, you may have to change the registry, the DUN object, or the phone
book entry, or all three.
The problem when the UART is not buffered is that the high speed inputs data to the UART faster than it
can handle, which causes a missed packet of data resulting in a 30-second retry. This can occur randomly,
but will be persistent. The slower speed reduces the exposure to an overrun of data and therefore no
more 30-second retries.
Unable to make a connection when infrared devices are installed: If the PC having connection
problems has infrared devices, you may need to disable infrared in some cases. Most of these devices
work from COM1 but fail to show up as using the associated hardware resources. Some experimentation
may need to be performed to isolate the problem during configuration of Operations Console.
Unexpected disconnections: If the PC, local or remote console, or both, have power management
capabilities, it should have this function disabled. Most PCs, and especially laptops, reset the
communications ports when invoking power management after the specified time. This would potentially
disconnect the established connection. Therefore, a local console that goes into power saver mode might
disconnect to the server and disconnect an active remote console.
Use HyperTerminal to validate connectivity between client and the server: HyperTerminal is a
Windows application used for connecting to various sources and is supplied by all Windows operating
systems on the install media, though may not be automatically installed. When the local console directly
attached to the server does not connect, you can use HyperTerminal to determine if the PC has
connectivity to the server.
Notes:
1. The data is slow to appear so be certain to allow a 15 - 20 seconds for an action to complete before
moving to the next step. Also keep in mind that some steps may not provide data to the window.
Wait a little time and then continue.
2. The following example was performed on a Windows 2000 PC. Other operating systems may have
slight differences in the presentation of options. The important part of this test is getting a response
back from the NEGOTIATE at the end of the document.
See the following to install and use HyperTerminal:
98
iSeries: iSeries Access for Windows Operations Console