If you can connect when "tserv" is the host name, but cannot connect when "tserv" is the computer name, then you may have a NetBIOS name resolution issue with WINS or an LMHOSTS file. If you can connect by replacing "tserv" with the Terminal Server's IP address but not the host name, you may have a DNS or WINS resolution problem. If Telnet reports that you cannot connect, there are several possible reasons: Telnet users can run a variety of character. Why does Telnet reports that you cannot connect? Telnet Server will turn a Windows NT/2000/XP/2003 system into a multi-user Telnet server giving Telnet users full access to Windows NT command line. This test tells you that you can connect over the port. The Terminal Server should disconnect the connection after a few minutes. Vt100/vt220/vt320/vt420/ssh terminal emulator for accessing to telnet servers. The Telnet connection will also consume an idle session.
On the Terminal Server, Terminal Server Administration will show a blue computer icon with no other information. If telnet is successful, you simply receive the telnet screen and a cursor. Where "tserv" is the host name of your Terminal Server. To test the functionality of port 3389, use this command from the Client: Telnet tserv 3389 It is written and maintained primarily by Simon Tatham. Test the functionality of port 3389 by using Telnet PuTTY is a free implementation of SSH and Telnet for Windows and Unix platforms, along with an xterm terminal emulator. Just try to telnet to the port from the Client. You can run a simple troubleshooting test to make sure the Client can connect to the port. A common problem in a WAN environment is that a firewall or other network filter prevents connectivity with this port. Terminal Server Clients use TCP port 3389 to communicate with Terminal Server.
#Free telnet server how to
This article describes how to use Telnet to test port 3389 functionality.
Use Telnet to test port 3389 functionality