Nlynx MinIT6000 Manual De Usuario

Descargar
Página de 127
3. Perceived 5250 Host Problems 
The first problems in this category are for when there are other users who have Telnet 
sessions working. 
Problem 3.1
 
You do not know the IP Address of the AS/400. 
Solution 
You will need access to the AS/400's command line from another terminal device or your 
system administrator to provide you with the correct IP address for the AS/400 that you 
want to connect to.  For those that don't know, or would like to know the AS/400 
command is as follows: 
1.  After signing on to the AS/400 with the appropriate privileges, from the command 
line type CFGTCP followed by the <enter> key. 
2.  On the next screen, select option Work with TCP/IP Interfaces, by typing a 1 and 
then <enter>
3.  Locate the interface that you are going to connect to. (If you only see 127.0.0.1 this 
means TCP/IP has not been properly configured on your AS/400.  DO NOT use 
127.0.0.1. 
If you do so you will NEVER get a sign on from the AS/400.  If TCP/IP is not configured 
on your AS/400 we recommend you follow the instructions from IBM.  The name of the 
book is called "Getting Your AS/400 Working for You".  Publication number is SC41-
5161-00.  You'll find helpful information on TCP/IP in Chapter 6.)  Write down the IP 
address and enter that in the MinIT 6000 configuration for this session’s Host 
Configuration – IP Address
Problem 3.2
 
It was working. The light on the MinIT 6000 is green.  The MinIT 6000 host session is 
black, with no cursor. 
Possible Cause 3.2.1
 
You have lost your IP connection. You could have a cable break, hub, bridge, or router 
down.  This means that you are not accessing a valid IP address, or the Ethernet line is 
not up or MinIT 6000 or the host configuration was changed. 
Action 
1.  Verify physical connection.  Viewing lights is the usually the quickest way to do this. 
2.  See if others users are working, if not check the AS400 configuration. 
3.  Swap devices if possible to see if the problem follows the device in question. 
Possible Cause 3.2.2
 
Disconnecting the session when you are not at a signon screen could cause this problem. 
This could also happen if you had a power outage and MinIT 6000 crashed and you had 
to re-boot.  The AS/400 still has your session active, although in a crashed status. 
Solution 
If the last device using this station address crashed, the station address may be varied off. 
Ask the System Administrator to vary your device on.  This may require varying off, then