Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am having issues running telnet in windows xp.

When I do:

Start > run > telnet > set localecho > set crlf > o 80

I get "Connecting to" and it never goes further. I can type, but I don't get any responses.

When I do:

Start > run > cmd > telnet 80

I can run http get and it returns html properly.

share|improve this question

migrated from Jan 7 '11 at 18:16

This question came from our site for system and network administrators.

What are you trying to accomplish? – Nathan Adams Jan 7 '11 at 16:40
Doing an example for MS certification exam 70-515. – P.Brian.Mackey Jan 7 '11 at 16:51
up vote 2 down vote accepted

Start > run > telnet > set localecho > set crlf > o 80

You actually really are connected to over port 80. Notice that your cursor is now at the top leftmost character space. If you start typing, you'll move the cursor and start typing over existing characters. Try that again, but use the following:

Start > run > telnet
set localecho
set crlf
o 80

You will then see the seemingly neverending "Connecting to" Next type:

GET / HTTP/1.1 [return]
Host: [double return]

Yes, that's my website. No, I'm not trying to pimp it. It's just that's what I'm certain will work since I was playing around with web browsing in telnet just a few days ago using my own site.

Why does Window's telnet work that way? What's with the funky way it positions the cursor depending on how you launch telnet? I don't know. It drives me mad. Let this be a lesson to never use Windows's built-in Telnet app and stick with PuTTY.

share|improve this answer
That's so odd that windows telnet behaves that way. Coming back from a site the text doesn't clear either. Very user unfriendly and seemingly very simple to fix with telnet via a cls (program itself, doing cls on our end is not recognized in telnet client). In fact, I think windows 3.1 had a better telnet than we have today in 2011... – P.Brian.Mackey Jan 7 '11 at 19:23

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .