Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I am connected in a telnet session in linux environment, but when I type commands and press enter, nothing happens. The TCP connection is in established state and when I checked the packets, the server is just echoing back whatever I typed and not taking any action.

Can anyone help?

share|improve this question
    
Why are you using telnet and not SSH? –  James O'Gorman Mar 3 '12 at 22:19
1  
Check your terminal settings. They are most likely wrong. Also it would help if you gave more info like what OS to/from, what telnet client, etc. –  kls Mar 3 '12 at 22:24
    
@JamesO'Gorman The session is in an isolated environment, not connected to internet; session is for testing purposes. –  Jake Mar 3 '12 at 22:26
    
@Jake Regardless of whether it's an isolated environment, telnet is highly deprecated and you're losing out on all the useful features of SSH. –  James O'Gorman Mar 3 '12 at 22:30

1 Answer 1

up vote 2 down vote accepted

To which port is your telnet session connected? If it's not port 23, you might just be connected to the echo service or something which is designed to do what you're seeing.

Otherwise, try pressing the break sequence (normally Control-], you may need to press return afterward) and do

send ayt

That should get an affirmative response if telnetd is working. You can try some other things (type "help" at the telnet> prompt to get some ideas).

If the telnet session seems to be working, what application software do you think you're connected to? Is that software working?

If you have access to the remote machine via some other mechanism, try investigating from that end (for example running strace on the user process your session is connected to). Failing that, ask the administrator of the remote machine.

Last, why on Earth are you still using telnet? Did you supply a password to log in? If yes, your password is in danger of being eavesdropped. You should almost certainly use ssh instead.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.