Telnet Proxy contents.gifprev1.gifnext1.gif

Telnet Proxy

Since Telnet is inherently a command-line based service, there is no special setup for the Telnet client. To use it however you must always first Telnet to the WinGate machine on the port you set up for the Telnet service. The standard port for Telnet is 23. You will then be presented with a prompt like this:

WinGate>

At this prompt, type in the name of the host you wish to connect to, and optionally a port number as well.
E.g.

WinGate>ftp.billy-sue.com

or

WinGate>ftp.billy-sue.com 1023

WinGate will display Connecting to …. When the Connected message comes back, you are connected through to the remote machine.

There have been a few changes with the WinGate telnet proxy, which affect telnet clients that issue telnet commands (e.g. EWAN, simpterm, and UNIX clients). You may get a double-echo while you are typing in the hostname you want to connect to. Once you are connected however, things should be alright again.

Some clients may also have problems with hitting the Enter key. Try Ctrl-J or Ctrl-enter. If that fails, try running the telnet service on a different port number. This sometimes tricks telnet clients into thinking they are not talking to a telnet server, and so they dont send the telnet commands that may confuse WinGate.

Note

The telnet server is has only one function - to connect you to a real telnet server. You cannot login or do any other functions usually associated with telnet. If you are always telnetting to the same host, you should use a mapped link instead - this will bypass having to type the host name in each time, and will allow full telnet option negotiation.

Adding a Telnet Proxy