Telnet Server Troubleshooting

  • Article

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

Troubleshooting

This section contains information on troubleshooting Telnet Server. For troubleshooting information on Telnet Client, see Telnet Client Troubleshooting.

What problem are you having?

  • Logon failure: The user has not been granted the requested logon type at this computer.

  • Access denied: Specified user is not a member of the TelnetClients group.

  • Logon failure: The user must change his or her password before logging on the first time.

  • Logon failure: Telnet Server allows NTLM authentication only.

  • Error while connecting to localhost: Could not open a connection to host on port 23.

  • Cannot connect to network drives.

  • Users cannot access drive letters mapped by others.

  • If you interrupt and then reconnect a Telnet session that is being conducted from a UNIX computer to a Windows-based computer, the cursor might lose alignment with the prompt.

Logon failure: The user has not been granted the requested logon type at this computer.

Cause:  The user does not have permission to log on locally to the computer running Telnet Server.

Solution:  Ensure that the user, or a group the user belongs to (such as the TelnetClients group), has the right to log on locally. Ensure that the user, or a group that the user belongs to, is not denied the right to log on locally.

Access denied: Specified user is not a member of the TelnetClients group.

Cause:  Users must belong to the TelnetClients group in order to connect to Telnet Server.

Solution:  Add the user to the TelnetClients group.

Logon failure: The user must change his or her password before logging on the first time.

Cause:  The user's password must be changed.

Solution:  The user must log on to the computer directly (that is, in person) to change the password.

Logon failure: Telnet Server allows NTLM authentication only.

Cause:  Either the client does not support NTLM authentication and the server requires it, or the client requires NTLM authentication and Telnet Server does not support it.

Solution:  If the Telnet client does not support NTLM authentication, use a client that does. If that is not possible, enable plaintext authentication on Telnet Server. For maximum security, use only Telnet clients that support NTLM authentication, and enable NTLM authentication and disable plaintext authentication on Telnet Server.

Error while connecting to localhost: Could not open a connection to host on port 23.

Cause:  Telnet Server is not configured to listen on port 23, or Telnet Server is not started.

Solution:  Ensure that Telnet Server is started and configured to listen on port 23. If that is not possible, specify the configured port after the host name when connecting.

Cannot connect to network drives.

Cause:  NTLM authentication does not allow access to network drives.

Solution:  Map the network to a drive letter using the net use /user command.

Users cannot access drive letters mapped by others.

Cause:  Telnet clients recognize only drive letters mapped during the current Telnet session. Consequently, Telnet users cannot access network drives using drive letters mapped by other Telnet users or by local server users.

Solution:  Telnet client users must use the net use /user command to map network drives to drive letters themselves.

If you interrupt and then reconnect a Telnet session that is being conducted from a UNIX computer to a Windows-based computer, the cursor might lose alignment with the prompt.

Cause:  This problem is caused by the interruption in communication.

Solution:  If your default shell is the Windows command prompt, type cls. If your default shell is the Korn shell or C shell, type clear.