Nlynx MinIT6000 - Manual (Page 120)

First, ping the MinIT 6000 from the AS/400:
1. Go to any command line, where it says:
Selection or command
===>
2. Type PING '###.###.###.###' (where ###.###.###.### is the IP address that you are
trying to reach, enclosed in single quotes)
3. You will get a message: "Verifying connection to host system ###.###.###.###". Put
your cursor on that message and ROLL UP (which is the Page Down key in some of
the better emulation packages).
4. If it says: " PING reply 1 from ###.###.###.### took 59 ms. 256 bytes. TTL 128",
then roll up again to check the next five. At the end it should say: "Connection
verification statistics: 5 of 5 successful (100 %)."
5. If it says "Unknown Host" or "No response from host within 1 seconds for connection
verification 1." you have a network problem that needs to be resolved.
Solution
If you can ping one way, but not the other, this is probably a router problem. If a router
table believes that a device is not on the network, it may misroute packets.
If the MinIT 6000 is at a remote site using a VPN connection to the host, make certain
that the default gateway for the AS/400 is set that of the router providing the VPN
connection.
Restart all routers and bridges.
If the IP address and subnet masks are logically on the same network, but you still cannot
ping, then there may be a physical break in the networks. If the subnet for the AS/400 is
not the same as the subnet for the MinIT 6000 Workstation, then they are on different
supernets and would need a router to connect.
Check your hubs. Try pinging other devices to see what devices you can reach, and what
the AS/400 can reach, to get a clue where the problem is. Look at the lights.
Problem 2.2
Tried to connect the MinIT 6000 and the host session is black, with no cursor. In the
taskbar on the lower right, there is an X through the network symbol.
Cause
The network connection is bad or disconnected.
Action
1. Verify that the network cable is inserted properly. There is an orange light when it is
connected properly.
2. Try swapping with a known good cable.
3. Make certain that any Hubs or Switches in the path to the Host are powered up.
4. Try another device in the TCP/IP connection.