Table of Contents
Advertisement
Local console does not detect console cable
These are solutions to problems that occur when the local console does not detect the presence of the
Operations Console cable. A status message of Connecting or Unavailable is usually present:
v Verify that the cable is properly connected. For more information, see Install Operations Console cables.
v For the console, verify that the communications adapter card on the server is properly located.
v Verify that the part numbers for the Operations Console cable is correct.
v Verify that the server is in a state such that the console would be active. For example, the console is
active after a manual initial program load (IPL). After you perform the IPL, the system reference codes
(SRCs) B6004031, B6004501, or B600500X (where x is a number) indicate that the server is in the proper
state.
v Verify that the resources of the PC 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 and make sure that the entry is:
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.
Old network data interfering with reconfiguration of network connectivity
If you are configuring a local console on a network and the user keeps getting an old IP address, which
may be wrong but you cannot get to it without changing the name, you may need to edit the hosts file
on the PC. You may need to edit the file and remove the entry in question.
Notes:
1. It is also suggested that you remove or alter the old entry in the hosts file on the PC. You can do a
search or find for hosts then double-click the file when it is found to start the default editor.
2. Operations Console should be closed and restarted before attempting to connect a new configuration.
This action will remove all cached values associated with any old configurations.
Unable to find correct modem at Add RAS Device selection
The user can be setting up a remote console or a local console in Windows NT. They have either recently
added or replaced a PC modem but are unable to find the item in the list of Add RAS device window.
Looking in RAS Properties should show another device on the same COM port. A typical scenario is that
during the installation of Remote Access Service, which is part of some Network installations, the user
will configure a nonexistent modem to complete the Remote Access Service installation, which requires a
modem. Later, during the setup of Operations Console, they need to add the AS400 Operations Console
Connection modem but it does not show up.
Solution: The current modem will have to be removed before the new modem is allowed to be presented
in that window.
In a similar case, you are switching from one type of configuration to another and during the initial steps
at determining what modems will need to be present for Remote Access Service the instructions have you
delete a modem. When you exit the Modem folder and get the message Dial-up Networking needs to be
configured because the list of installed modems has changed. Would you like to do this now? If
you answer with a Yes the result is that Remote Access Service and the modem list is out of sync. To fix
this:
1. Go into Remote Access Service.
2. Remove the same modem.
3. Click Continue.
4. Answer the appropriate messages and reboot.
5. Return to Remote Access Service and continue with the instructions to add the modem that you could
not before.
107
Operations Console
Advertisement
Table of Contents
