Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
The thing is I can log on to Linux machine from XP through Telnet using a user account but can't using root. I'm using the same root account including the same root password. But while I'm logged on as normal user, then if i use the 'su' command it prompts for password and that time the root password does work.
Why is that and how can log in as root from XP? THANX.
Damn, now got new problem, the connection is lost after a while if i don't do anything. The connection just automatically closes. What is this bullllsss???
(1) Logging on using telnet is a very bad idea as your password is transmitted in plain text. Therefore it's a very very bad idea to login as root using telnet. You should use SSH instead. If you absolutely must log in as root using telnet, you'll have to edit the /etc/securetty file and add some of the virtual terminals like pts/0, pts/1, etc. (ttyp0, ttyp1, etc. on systems not using Unix98 style PTYs). As I said above this is not a good idea except in certain highly trusted environments.
(2) Do you have auto-logout set in your shell? is there an intervening firewall that could close the connection after a certain amount of time with no traffic?
I added some more terminals but still the same problem. Also my Linux Firewall is Off and how will i check that if auto-logout is set or not? i checked 'env' and there was nothing like auto-logout thing. Could it be that XP is cutting the connection?
Here is my penultimate session:
Fedora Core release 1 (Yarrow)
Kernel 2.4.22-1.2115.nptl on an i686
login: root
Password:
Login incorrect
login: asif
Password:
Last login: Wed Oct 29 13:34:45 from 172.16.113.77
[asif@localhost asif]$ ls
z.txt z.txt~
[asif@localhost asif]$ ls
Connection to host lost.
** Note that i was inactive for around 3 minutes.
And This my last session:
Fedora Core release 1 (Yarrow)
Kernel 2.4.22-1.2115.nptl on an i686
login: a
Connection to host lost.
** see, even before start typing the connection was lost.
Distribution: OpenBSD 4.6, OS X 10.6.2, CentOS 4 & 5
Posts: 3,660
Rep:
Step 1: Download PuTTY
Step 2: Forget about telnet entirely and use only SSH (PuTTY). telnet is entirely unsafe and anyone knowledgable will giggle at you for using telnet. You might as well learn how to do things The Right Way(tm) the first time around, rather than having to unlearn the wrong way first.
Distribution: OpenBSD 4.6, OS X 10.6.2, CentOS 4 & 5
Posts: 3,660
Rep:
Well post the errors you had with PuTTY so you can fix the right thing. Fixing telnet is like fixing a broken self-destruct button that has already been pressed.
I agree with previous posters with regards to telnet access (unless it's for a box in your own local network at home or, as indicated by btmiller, a highly trusted network).
Root access using telnet is probably blocked (and I don't know where it can be set). As you have access as normal user, use that and next su to root.
Even if you use SSH, you should use that approach (block direct root access) as it creates an additional barrier for attackers.
you'll have to edit the /etc/securetty file and add some of the virtual terminals like pts/0, pts/1, etc. (ttyp0, ttyp1, etc. on systems not using Unix98 style PTYs).
Thanks Man
It was a great help !!!
One more thing, file permission for /etc/securetty should be 644 only...
I had tried with 777 and had run into problem.
One point as a side note, in most of the posts, i found that people suggesting SSH to use... I really dont understand when someone is asking to solve telnet problem, ppl are trying to sidetrack the problem rather than helping on this front....
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.