### Telnet: Receiving No Login Prompt

Use this troubleshooting procedure to verify the connection when you performed a telnet to the PortServer and did NOT receive a PortServer login prompt.

If you can find no problem at the end of each step in this procedure, continue with the next step. If there is a problem, fix it and check to see of the RealPort devices are working. If they are, you should have resolved the problem. If they are not, go back to the Master Troubleshooting Process.

#### Procedure

1. Turn off the PortServer and issue the ping command,

> > `ping ipaddress`

> If it fails (you do not receive a response), continue with this procedure.

> If it succeeds (you received a response), this indicates there is another system using the same IP address. In this case, you need to assign another IP address to the PortServer.

2. From a terminal directly attached to the PortServer, check the configuration by entering the command:

> > `set config`

> Verify the IP address, the mask settings, the gateway and that the RealPort setting is 771.

3. Check the Ethernet cable. Verify the following:

> - The Ethernet cable is connected securely at both ends.
> - The Ethernet cable is pinned correctly.
> - The quality of the cable is sufficient for the cable length and the cable environment.

> Note: Common Category 5 Unshielded Twisted Pair cabling can generally be run 300 meters at a speed of 10 Mbps and 150 meters at higher speeds. Consult an Ethernet cable manufacturer for a recommended cable for your configuration.

> IMPORTANT! If you are using a 10/100 hub, PortServer only supports a 10 megabit Ethernet network.

4. If you are using a Thinnet (10Base2) cable, make sure the cable selector switch on the PortServer is in the left-handed position.

> If you are using a Twisted Pair (10Base2) cable, make sure the cable selector switch on the PortServer is in the right-handed position.

5. Verify your Ethernet hub. See your Ethernet hub manual.
6. If there is still a problem, choose Back to return to and continue with the Master Troubleshooting Process.