Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
I'm having a hard time mastering this: I've just installed Debian Lenny into two new servers, and gone no further than installing OpenSSH-server (to accept remote ssh connections). My problem is that I'm getting network periodically hangs when I try to ssh from one of our remote-desktop-controlled "head" servers (Leopard Server 10.5.8). Here are the symptoms:
a) If I connect in ssh and start typing commands, there comes a point where I can no longer communicate new text through ssh. If I leave the terminal window open, I eventually get a message: "dRead from remote host server.ourdomain.com: Operation timed out
Connection to server.ourdomain.com closed."
b) Should I try immediately to connect, after a delay I get a message "ssh: connect to host server.ourdomain.com port 22: Operation timed out
c) Should I just connect to the server, not type any commands, and leave the connection open, I can come back even days later and be able to begin to send commands, but after a few the connection behaves like symptom a)
In all of the cases above, I can still ping the server I am trying to connect to.
Does the above seem familiar to anyone here, and could anyone tell me where to look (and what tools to use to do so)? Could this also be because of faulty DNS in the head server (I checked everything, as I had attributed new LAN IP's to the "sub servers" - but perhaps a mismatched MAC address?).
In any case, I'm really stumped, so if anyone can help, thank you very much.
PS: the "sub-servers" are Dell PE 1950's - there was an issue because of a "non-free" firmware (bnx2 for the gigabit ethernet card) not included in the default distribution, but normally I installed this just fine. Perhaps there is an issue there too?