43

on Windows XP/server 2003

When telnet some remote host on a specified port, after connection established, sometimes press ctrl+] doesn't quit. Is there any command can quit instead of just close the command line window? Thanks.

EDIT: But sometimes even type ctrl + ], telnet command line doesn't show up, still stuck at the blank screen.

Stan
  • 1,367
  • 6
  • 24
  • 40

10 Answers10

56

ctrl+] is an escape sequence that puts telnet into command mode, it doesn't terminate the session. If you type close after hitting ctrl+], that will "close" the telnet session.

chicks
  • 3,639
  • 10
  • 26
  • 36
Alex
  • 6,477
  • 1
  • 23
  • 32
  • Weird, Ctrl+] doesn't seem to work. Also, why do you type `close` instead of simply typing `q`? – Pacerier Jul 03 '15 at 04:08
  • I think of them as "opening" and "closing" connections rather than "quitting" a session. If you run telnet by itself with no other options, you would use `open host.domain.com`. So to me, `close` is `open`'s obvious partner and just makes more sense. However, `q` also works, and is certainly fewer letters :) – Alex Jul 06 '15 at 04:06
  • close takes me to `Microsoft Telnet>` and `q` or `quit` takes me to `C:\Windows\system32>` – Sohail Ahmed Dec 26 '16 at 09:37
17

on German keyboards the following keystrokes will help

CTRL + +

or rather

Strg + +

Norbert Weuster
  • 181
  • 2
  • 8
8

You can use the 'quit' command, or abbreviate it to just 'q' if you like.

Cypher
  • 1,079
  • 2
  • 17
  • 24
3

The solution worked for me is

CTRL $

Then after when you will be in telnet invite type

quit 

then enter to exit from telnet and return to your DOS invite

abk
  • 31
  • 2
2

I'm not terribly familiar with Windows telnet, but local behavior on non-Windows boxes using telnet is a combination of the telnet state and that of the terminal or enclosing window and shell. (If your remote connection has changed the echo mode, font color, interrupt status, and etc, killing telnet has no effect on that local status.)

Does Windows have similar local status? (I assume so, or most text editors and many other programs wouldn't work in telnet windows.)

For Unix, the typical sequence was Ctrl]quitreturnstty sanereturn to get local control and tty sanity. What's the Windows equivalent of "tty sane"?

Pacerier
  • 511
  • 15
  • 35
mpez0
  • 1,492
  • 9
  • 9
1

ctrl+] will take you to command mode if the telnet client is already connected; from there you can type (q)uit to exit.

If it's connecting, however (or failing to connect...), then there is no way to interrupt the process until it times out.

Mikeage
  • 2,731
  • 6
  • 26
  • 37
1

Standard way of disconnecting the line in most applications is ~+., keep in mind, that often this has to be typed in blindly, so press enter a couple of times: Enter+~+..

This is also the standard way of closing the connection on an SSH session, that became unresponsive.

polemon
  • 565
  • 2
  • 8
  • 21
  • Doesn't work: `Invalid Command. type ?/help for help` – Pacerier Jul 03 '15 at 04:08
  • 2
    tilde then dot was used by `rlogin`, and subsequently by `ssh` (at least on Unix); it was not and is not used by `telnet`. (Some programs like `ed`, and some protocols like SMTP and NNTP, use a *line* containing only dot to terminate data.) Most `telnet` clients, including Windows, default to ctrl-] but can be set to something else. – dave_thompson_085 Nov 30 '15 at 14:23
1

On a French keyboard I have to use ctrl+$

Then 'quit' from the resulting telnet prompt.

Martin R
  • 11
  • 1
0

maybe with ctrl + d ?

Nikolaidis Fotis
  • 1,994
  • 11
  • 13
0

At least in my Linux system, the only way to exit from a telnet session is by using the following keys (pressing the 3 keys together: Ctrl, AltGr,+ and then the following prompt appears: telnet> Now press the key q and the telnet session will be terminated.