When some Telnet Server faults occur, what measures should we solve? Let's take a look at this issue. First, we listed some fault problems. In addition, we analyzed and diagnosed these problems and hoped that the proposed solution could help you.
Unable to connect to the network drive using the current login creden
Application to: Windows Server 2008
When you use NTLM authentication and the user ID and password also grant it the access permission to the network resources on another server in the network of the Telnet server) to log on to the Telnet server, this problem usually occurs.
Diagnosis
Due to NTLM authentication restrictions, the Telnet server cannot automatically pass creden. to the server hosting network resources.
Solution
From the Telnet Client Session, connect to the network resource of the credentelnet to be used, even if these creden. are the same as the creden. used to log on to the Telnet server. for example, if the resource is a mapped drive, you can use the following command to request the ing of a specific user ID:
Net user x: \ Server Name \ Share Name/user: user name and password
You can use an asterisk (*) to replace the password so that Windows security prompts you, instead of typing a password on the command line, and then display the password on the screen.
Unable to access the drive letter mapped by other sessions in a separate Telnet session
Application to: Windows Server 2008
This problem usually occurs when multiple users log on to the Telnet server. one user maps one or more network resources to drive letters, and the other user expects these drive letters to be used by all users on the Telnet server.
Diagnosis
The drive letter of the mapped network resource is reserved for each user, but the user accounts are not shared. Only the physical drive attached to the Telnet server can be used by all users depending on the user's security permissions ).
Solution
Each user must use the net use or net user command to map the network drive to the drive letter according to their own needs.
The characters and lines displayed on the Telnet client are not aligned.
Application to: Windows Server 2008
This problem causes unexpected location of text in the Telnet window.
Diagnosis
This problem may be caused by the mismatch between the size of the Telnet client window and the maximum size of the command window supported by the Telnet server. the size of the Telnet client window is determined by the setting of the Command Prompt window used to start the Telnet client. the expected window size of the Telnet server is determined by the terminal simulation settings used in the current session. if Telnet simulates 80 columns of display and your client window is narrower or wider than 80 columns, the text may wrap or cannot wrap as expected by the server, as a result, the display is not arranged as expected.
Solution
Make sure that the Telnet client window is set to the Telnet server and the expected size of the terminal type being simulated.
To adjust the window size of the Telnet Client
Click the command prompt icon in the upper-left corner of the Telnet client window, and then click "default settings" or "properties ":
If you select "default settings" set by the server, you need to change the values of all Command Prompt Windows. These windows are started in the same shortcut as the windows to be modified ).
If "attribute" is selected, only the current Command Prompt window is affected.
On the "layout" tab, select the "window size width" and "height" values that match the current terminal simulation in the session. the default value is "width: 80" and "height: 25.