This topic explains how to connect a local console that is directly
attached to a server with remote access allowed, allowing remote consoles,
through dial-up support, to access and control the server.
It also allows Server control to be
automatically granted to the first requester or allows you to have control
at the local console to handle incoming control requests.
Perform the
following steps to connect a local console that is directly attached with
remote access allowed:
- Open Operations Console to start the connection:
- Click Start and select Programs.
- Select IBM iSeries™ Access
for Windows.
- Click Operations Console.
By default, Operations Console does not automatically try to connect
a local console that is directly attached. However, a local console that is
directly attached with remote access allowed running in unattended mode automatically
connects. If you selected Start connection when Operations Console
starts in Properties, the locale console connects to the server
automatically. The connection status displays Connecting before
changing to Connecting Console.
- If you set up your local console configuration to start in attended
mode, do the following:
- In the Service Device Sign-on window, sign
on using your assigned service tools user ID and password. Operations
Console needs a valid service tools user ID and password to authorize the
connection between the server and the PC. If you have problems when signing
on, see Troubleshooting authentication problems. After you sign
on successfully, the status changes from Pending Authorization to Connected.
- Confirm that the console displays. If the emulator
does not appear, see Troubleshooting emulator problems.
- If you set up your local console configuration to start in unattended
mode, verify that the status displays Pending
Authorization and that SERVER displays
in the Current User field. Incoming control
requests will be automatically granted.