### Telnet: Receiving a Login Prompt

Use this procedure during the Master Troubleshooting Process when you performed a telnet to the PortServer and did receive a PortServer login prompt.

#### Procedure

1. Log in as root. The default password is dbps.
2. Check to see that the required information appears in your port settings by using the following commands:

> Command | Requirement
> --- | ---
> `set port range=range` where `range` is two numbers separated by a hyphen. The first number is the beginning range and must be less than the second number. Often the number is 1. The second number is the end range and is between 8 and 64. | prn or rp must be in the dev column. IMPORTANT! All set port parameters must be factory default. Go to Example: set port Command for an example of the result of choosing a set port range that equals 1-16.
> `set flow range=range` where `range` is two numbers separated by a hyphen. The first number is the beginning range and must be less than the second number. Often the number is 1. The second number is the end range and is between 8 and 64. | If you are using an 8-wire modem cable or if your operating system is AIX, HP-UX, Solaris, or SCO UnixWare/SVR4, the altpin column must display on. Note: If you are using an RJ-45 10-pin modem cable, the Flow Range setting must have off in the altpin column. Go to Example: set flow Command for an example of the result of choosing a set flow range that equals 1-16.
> `set auth` | In the RealPort column, the set auth value should be set to o for each RealPort port. Go to Example: set auth Command for an example of the result of using the set auth command.

3. If your port settings match the above requirements, choose Back to return and continue with the Master Troubleshooting Process.

> If your port settings do not match the above requirements, you need to change the port or a group of ports to be available for RealPort. See the PortServer II Command Reference Guide for more information. Once you've changed the port settings and the devices still don't work, go through the Master Troubleshooting Process again.