Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Hey, it works! - sort of. After I did all that with the keys, I logged, and it never did a thing afterwords. It didn't even give me a prompt. The log for my SSH client said that the login was successful. Now when I try to log in it does nothing until the connection times out. What's wrong now?
hmm.... very strange.... with PuTTY, it does the following steps:
1. PuTTYonnects to TCP/IP port.
2. PuTTY prompts for username.
3. PuTTY sends username to server, and waits for password prompt response.
From this point on, PuTTY isn't doing anything except displaying what the remote server throws at it.
Therefore, the password prompt comes from the SSH server you are connecting to... which indicates that the daemon is working and running.
I have absolutely no idea why it times out after logging in though. Have you tried creating a new normal user account, and using that to log in with? it could be a weird issue with your own user account.
ok... a possible reason for it not working before was that you were logging in as root.... (that's how i read it anyhow) remote logins as root are not permitted on most machines.
when you say it logged in fine with user 'travis', you said it told you your last login, but then did nothing... what do you mean "nothing"?? did it give you an error? did it time out? did PuTTY display a dialog box?
nah... that's all u need to do to enable remote root logins. it's not recommended though, of course
as for it timing out... it sounds like your daemon is crashing, maybe... it is active to begin with (cos it asks for your password), but then it times out, so i think it's hanging or crashing.
does your machine have a *really* high load on it, or did you compile the SSH daemon yourself??
SSH installed when Linux installed, and I'm the only one accessing my PS2. It isn't even hooked up to the Internet.
However, I was thinking that since the Playstation 2 probably has the biggest ratio of CPU power to RAM (~5 Gigaflops/32 Mb), I'd try it without X running. It got a little bit further this time. The output is as follows:
login as: travis
Last login: Mon Aug 4 19:04:20 2003 from 10.0.0.2
[travis@pstwo travis]$ ls -al
drwx------ 12 travis travis 4096 Aug 4 18:54 .
drwxr-xr-x 7 root root 4096 May 22 19:58 ..
-rw------- 1 travis travis 0 May 23 18:59 .ICEauthority
-rw------- 1 travis travis 99 Aug 4 18:50 .Xauthority
-rw-r--r-- 1 travis travis 4846 May 22 19:58 .Xdefaults
-rw------- 1 travis travis 160 Aug 4 21:43 .bash_history
-rw-r--r-- 1 travis travis 24 May 22 19:58 .bash_logout
Then after about five seconds, it said "Connection reset by peer." You can see that it says "total 152", so it didn't even finish "ls -al" before it quit.
A 286 could probably do SSH and X at the same time without crashing, so I doubt this is the matter.