These are solutions to problems that occur when the local console
does not detect the presence of the Operations Console cable.
If this problem exists, a status message of
Connecting or
Unavailable is
usually present or the port detection in the setup wizard fails.
- Verify that the cable is connected correctly. For more information on
cable installation, see Installing an Operations Console cable.
- For the console, verify that the asynchronous communications adapter on
the server is located correctly.
- Verify that the part numbers for the Operations Console cable is correct.
- Verify that the server is in a state such that the console is active.
For example, the console is active after the server is started. After you
start the server, the system reference codes (SRCs) B6004031, B6004508, or
B600500x (where is a number) indicate that the server is
in the correct state.
- Verify that the PC resources are free of address or interrupt request
(IRQ) conflicts. Operations Console uses addresses in the range of 192.168.0.0
to 192.168.0.255. If you run any software that makes your PC SOCKS-enabled,
check your SOCKS configuration:
- Direct 192.168.0.0 255.255.255.0
- A SOCKS-enabled PC accesses the Internet through a firewall, such as Microsoft® Proxy
Client, Hummingbird® SOCKS
Client, or others.