Unable To Find Correct Modem At Add Ras Device Selection; Troubleshoot Other Operations Console Problems; Operations Console Remains In Qctl - IBM E Server i Series Manual

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

Troubleshoot other Operations Console problems

When using Operations Console you can encounter the following problems:

Operations Console remains in QCTL

This usually shows up after a migration but could be found at any time you have
been working with resources. QCONSOLE still remains in QCTL when you would
have expected it to be reassigned as another workstation. Be sure that the system
has not been IPLed with DEBUG turned on. A good indication is that no other
interactive subsystem has started, if present, and others may also be absent. Check
SYSVAL QIPLTYPE it should be 0.
114
iSeries: iSeries Access for Windows Operations Console
modem that you could not before.
Operations Console remains in QCTL
Solutions for when Operations Console remains in QCTL when it should be
CTLxx.
Local console receives message: Remote Access Service server did not start
Solutions for when the local console gets Remote Access Service Server did
not start message (Windows NT only).
System requests will not work
Solutions for when system requests will not work.