Hi, I've enabled xinetd, and toggled telnet to active in yast. I've then tried to telnet into my machine from another one on the same network but it is saying could not open connection to the host. Is there something else I need to enable? I can ping between the machines Phil
On Thursday 19 October 2006 18:25, Phil Burness wrote:
Hi, I've enabled xinetd, and toggled telnet to active in yast.
I've then tried to telnet into my machine from another one on the same network but it is saying could not open connection to the host.
Is there something else I need to enable?
I can ping between the machines
Phil
Have you allowed the telnet service in your firewall config? Why would you want telnet anyway it's not secure, can't you use SSH/SCP instead? Matthew
On Thursday 19 October 2006 13:33, Matthew Stringer wrote:
I can ping between the machines
Phil
Have you allowed the telnet service in your firewall config?
Why would you want telnet anyway it's not secure, can't you use SSH/SCP instead?
Because he might have devices that only use telnet. Like my two webcams. Be sure you have cycled Xinet.d after making any changes to its tables.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2006-10-19 at 13:45 -0400, Bruce Marshall wrote:
Why would you want telnet anyway it's not secure, can't you use SSH/SCP instead?
Because he might have devices that only use telnet. Like my two webcams.
For that you need the telnet client, but not the telnet server. You don't need to change xinet to make user of the client. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFN8VFtTMYHG2NR9URAlf2AJwPOVvMiWqN2wcNU9HeVqW+u9XIswCfbwxw Ne5XAGJAaxefmlRCL040e+k= =tIY4 -----END PGP SIGNATURE-----
On Thursday 19 October 2006 14:34, Carlos E. R. wrote:
Because he might have devices that only use telnet. Like my two webcams.
For that you need the telnet client, but not the telnet server. You don't need to change xinet to make user of the client.
Well, if he wants to telnet from one box to another, then he needs a server. And then we're back to "Why do you want to use telnet?"
Bruce Marshall wrote:
On Thursday 19 October 2006 14:34, Carlos E. R. wrote:
Because he might have devices that only use telnet. Like my two webcams. For that you need the telnet client, but not the telnet server. You don't need to change xinet to make user of the client.
Well, if he wants to telnet from one box to another, then he needs a server.
And then we're back to "Why do you want to use telnet?"
Well, at work I often have to telnet to devices that don't talk SSH. There are many such devices. In fact I'm currently involved in such a project at work. I can use SSH to reach one box and from there, I have to use telnet to reach the other.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2006-10-19 at 19:35 -0400, James Knott wrote:
Well, at work I often have to telnet to devices that don't talk SSH. There are many such devices. In fact I'm currently involved in such a project at work. I can use SSH to reach one box and from there, I have to use telnet to reach the other.
But in those cases, you do not need to setup a server, you only need a client in the machines you're telneting from. So what Bruce said is very valid:
And then we're back to "Why do you want to use telnet?"
meaning the OP, of course. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFOCJ4tTMYHG2NR9URAoYnAJ0W/kkp4wGNeVByGjB3VR/Kfhf95QCggnT+ 1J+TATXbOiFdyb+OtK1SUOw= =/ji3 -----END PGP SIGNATURE-----
On Thursday 19 October 2006 19:48, Bruce Marshall wrote:
On Thursday 19 October 2006 14:34, Carlos E. R. wrote:
Because he might have devices that only use telnet. Like my two webcams.
For that you need the telnet client, but not the telnet server. You don't need to change xinet to make user of the client.
Well, if he wants to telnet from one box to another, then he needs a server.
And then we're back to "Why do you want to use telnet?" I am on a private network and am too lazy to walk upstairs every time I want to access my Linux machine, so I wanted to be able to telnet in from my laptop downstairs :-) As I'm on a private network security is not an issue, and there is only me usingthe machines, apart from my 7 year old daughter who prints via the Linux box. She hasn't grasped telnet yet.
I now have it working, thanks to the good advice I've received. I enabled telnet in xinetd - it prompted for and installed the telnetd server. I opened port 23 on the firewall. I was then able to telnet in from my laptop using the telnet client in XP. I can now be as lazy as I like :-) Thanks Phil
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2006-10-20 at 09:02 +0100, Phil Burness wrote: ...
I was then able to telnet in from my laptop using the telnet client in XP. I can now be as lazy as I like :-)
You could have been even lazier using ssh/sshd, as it is already installed and configured by default (except the firewall) :-P - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFOKAntTMYHG2NR9URAriFAJ0awbJl08Bu0T4lMWQXnIvGfyVSLgCePvFm fF41Mm0rW/0Yf1RLHlcZMuQ= =mPgm -----END PGP SIGNATURE-----
I was then able to telnet in from my laptop using the telnet client in XP. I can now be as lazy as I like :-)
You could have been even lazier using ssh/sshd, as it is already installed and configured by default (except the firewall) :-P
At 05:08 AM 10/20/2006, Carlos E. R. wrote: then he would have to download putty the free ssh client for windows. I only use telnet to connect to devies that need it an ssh for everything else. jack
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2006-10-20 at 06:13 -0500, Jack Malone wrote:
You could have been even lazier using ssh/sshd, as it is already installed and configured by default (except the firewall) :-P
then he would have to download putty the free ssh client for windows.
Wich is a good thing to have, anyway. It is included in the comercial SuSE DVD, by the way. Or was, at least. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFOPALtTMYHG2NR9URAso+AKCIE+5zwIC5twFz1s5GvIIZ5l4dQQCgi4GE JkcPfFtkzDdax87YotA+GS8= =ba+0 -----END PGP SIGNATURE-----
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Friday 2006-10-20 at 09:02 +0100, Phil Burness wrote:
...
I was then able to telnet in from my laptop using the telnet client in XP. I can now be as lazy as I like :-)
You could have been even lazier using ssh/sshd, as it is already installed and configured by default (except the firewall) :-P
There are valid reasons for using telnet verses ssh on an internal network. The primary reason I do is because it is much faster. Telnet is not going to encrypt everything. Try transferring a file via scp and do the same via rcp. The difference can be substantial, depending on the processor. -- Until later, Geoffrey Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. - Benjamin Franklin
On Tuesday 24 October 2006 16:41, Geoffrey wrote:
There are valid reasons for using telnet verses ssh on an internal network. The primary reason I do is because it is much faster. Telnet is not going to encrypt everything. Try transferring a file via scp and do the same via rcp. The difference can be substantial, depending on the processor.
Not only the speed difference, but watch the processor load. scp normally takes large amount of the CPU. Here's a trick i regularly use to ease that problem, without having to resort to rcp: i often watch videos while i copy them to another machine (using scp) to be burned to DVD (my desktop machine didn't, until recently, have a DVD burner). When i do this, scp takes up so much CPU that my videos drop frames or the audio drops out for short periods. To get around that, simply renice your scp process: nice -+19 scp myfile remote:/path/to/myfile -- ----- stephan@s11n.net http://s11n.net "...pleasure is a grace and is not obedient to the commands of the will." -- Alan W. Watts
stephan beal wrote:
On Tuesday 24 October 2006 16:41, Geoffrey wrote:
There are valid reasons for using telnet verses ssh on an internal network. The primary reason I do is because it is much faster. Telnet is not going to encrypt everything. Try transferring a file via scp and do the same via rcp. The difference can be substantial, depending on the processor.
Not only the speed difference, but watch the processor load. scp normally takes large amount of the CPU. Here's a trick i regularly use to ease that problem, without having to resort to rcp:
i often watch videos while i copy them to another machine (using scp) to be burned to DVD (my desktop machine didn't, until recently, have a DVD burner). When i do this, scp takes up so much CPU that my videos drop frames or the audio drops out for short periods. To get around that, simply renice your scp process:
nice -+19 scp myfile remote:/path/to/myfile
And the following week, the files have arrived! -- Until later, Geoffrey Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. - Benjamin Franklin
On Tuesday 24 October 2006 18:03, stephan beal wrote:
i often watch videos while i copy them to another machine (using scp) to be burned to DVD (my desktop machine didn't, until recently, have a DVD burner). When i do this, scp takes up so much CPU that my videos drop frames or the audio drops out for short periods. To get around that, simply renice your scp process:
nice -+19 scp myfile remote:/path/to/myfile
If I/O bandwidth, rather than CPU, is the problem, then the ionice command would also be useful. -- Bill Gallafent.
Phil Burness wrote:
And then we're back to "Why do you want to use telnet?" I am on a private network and am too lazy to walk upstairs every time I want to access my Linux machine, so I wanted to be able to telnet in from my laptop downstairs :-) As I'm on a private network security is not an issue, and there is only me usingthe machines, apart from my 7 year old daughter who prints via the Linux box. She hasn't grasped telnet yet.
Why not use SSH?
I now have it working, thanks to the good advice I've received. I enabled telnet in xinetd - it prompted for and installed the telnetd server. I opened port 23 on the firewall.
I was then able to telnet in from my laptop using the telnet client in XP. I can now be as lazy as I like :-)
You can use Putty to SSH from Windows.
On Friday 20 October 2006 04:02, Phil Burness wrote:
On Thursday 19 October 2006 19:48, Bruce Marshall wrote:
On Thursday 19 October 2006 14:34, Carlos E. R. wrote:
Because he might have devices that only use telnet. Like my two webcams.
For that you need the telnet client, but not the telnet server. You don't need to change xinet to make user of the client.
Well, if he wants to telnet from one box to another, then he needs a server.
And then we're back to "Why do you want to use telnet?"
I am on a private network and am too lazy to walk upstairs every time I want to access my Linux machine, so I wanted to be able to telnet in from my laptop downstairs :-) As I'm on a private network security is not an issue, and there is only me usingthe machines, apart from my 7 year old daughter who prints via the Linux box. She hasn't grasped telnet yet.
I now have it working, thanks to the good advice I've received. I enabled telnet in xinetd - it prompted for and installed the telnetd server. I opened port 23 on the firewall.
I was then able to telnet in from my laptop using the telnet client in XP. I can now be as lazy as I like :-)
But ssh is probably still the way to go.... for instance you can do X tunneling as well as a lot of other tunneling I haven't even explored. And you can set it up to know your password so a simple 'ssh <machname> will get you logged on. Plus... if you set it up to allow it, you could ssh from a remote machine with plenty of security.
Phil Burness wrote:
Hi, I've enabled xinetd, and toggled telnet to active in yast.
I've then tried to telnet into my machine from another one on the same network but it is saying could not open connection to the host.
Is there something else I need to enable?
I've just tried to go thru the same, and my default (10.1) xinetd config does not have a telnet config. I would check /var/log/messages and see if xinetd does actually set up for telnet. If not, I would check if your system has got telnetd installed. Firewall - check that the server machine allows inbound tcp traffic on port 23. Per Jessen, Zurich -- http://www.spamchek.com/ - managed email security. Starting at SFr5/month/user.
participants (10)
-
Bruce Marshall -
Carlos E. R. -
Geoffrey -
Jack Malone -
James Knott -
Matthew Stringer -
Per Jessen -
Phil Burness -
stephan beal -
William Gallafent