telnet...

sausage butty · 22-02-2009, 19:11

dooes anybody know why my pc does not recognise telent as a command in command promt!!!

running vista premium.

thanks in advance.

K.S.H · 22-02-2009, 19:19

Quote:

Originally Posted by sausage butty

dooes anybody know why my pc does not recognise telent as a command in command promt!!!

running vista premium.

thanks in advance.

Quick search shows its not turned on by default in Vista

Click on Start button, then go to Control Panel -> Programs.
Under the Programs and Features section, click Turn Windows features on or off. If User Account Control permission confirmation request warning pops up, click on Continue. If you are prompted for an administrator password, type the password.
In the Windows Features dialog box, select (tick) the Telnet Client check box.

sausage butty · 22-02-2009, 19:26

thanks . any idea why it isnt istalled by default?

K.S.H · 22-02-2009, 19:29

No idea, Bill has some strange ideas

andrewb · 22-02-2009, 22:04

Probably because SSH is far more secure.

Neil · 22-02-2009, 23:53

Quote:

Originally Posted by sausage butty

thanks . any idea why it isnt istalled by default?

I would agree with Andrew. You can sniff the network and see everything you type in a telnet session in clear text including your username and password

entwisi · 23-02-2009, 09:18

you should never use telnet apart from the useful bit of telling if something is listening ona specific port. ie.. is a webserver/etc up and running. Telnetting to the relevant port ( 80 or 443 by default but not always!) you will get a connected reply.

if you are logging onto another box always sue ssh.

K-P · 23-02-2009, 09:35

all them yrs using telnet to be told now you should never use it..

ssh on a fixed IP ...deffo

Neil · 23-02-2009, 09:54

It does of course all depend on what you are doing. If you want to telnet into your home router on a wired network then you are safe, unless someone sneaks in and plugs a cable into your router while you are not looking

entwisi · 23-02-2009, 11:11

but then you have the behaviour in your head, better to never use it and then you are never tempted to ever type the command.

In some cases at our work telnet is aliased to ssh JUST IN CASE and thats on fully protected secure networks. We aren't even allowed to send anything in clear across a network cable in our secure data centre. even calls back to the same box over http MUST use SSL encryption or our audit boys shut the service down till its is.

Neil · 23-02-2009, 22:37

Quote:

Originally Posted by entwisi

but then you have the behaviour in your head, better to never use it and then you are never tempted to ever type the command.

In some cases at our work telnet is aliased to ssh JUST IN CASE and thats on fully protected secure networks. We aren't even allowed to send anything in clear across a network cable in our secure data centre. even calls back to the same box over http MUST use SSL encryption or our audit boys shut the service down till its is.

That is understandable in your enviroment.