Of course, this is just a simple example but I am sure that there are many examples in your own organization where your administrative task could get done quicker if you could just telnet to the Windows server and perform the CLI commands that you need to perform. For example, instead of connecting to the server with Remote Desktop (RDP), with VNC, or another remote control method, why not just telnet to the server and quickly run the 2 commands that you need to run? There are a few quick commands that I can do to check on those files and I could do those commands much quicker than other alternatives if I could just get to a Windows command prompt. Say that I want to check on the status of some files that are supposed to be transmitted to my IIS server.

To test connectivity to and from the server using a simple & reliable protocol.

To be able to configure and troubleshoot all your network devices – whether they are Cisco routers, Linux servers, or Windows 2008 Servers, from a quick and simple command line – that is the telnet application.

To perform remote CLI commands on your Windows 2008 Server, over a LAN or a WAN.

There are a number of reasons to configure a Windows 2008 Server as a Telnet server. Why would I want to configure my Windows 2008 Server as a Telnet Server? Now, let’s find out how to configure both! In Windows Server 2008, configuring your server to respond to telnet requests and even using a Windows 2008 Server to telnet to another system with a telnet server can be quite different. While the telnet client and server application has been around, well, forever, it is still very useful and, if you are like me, you may use it every day for a variety of network configuration tasks.

Secure telnet server