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 problem getting and ssh connection to a particular Linux box at my school. The putty terminal opens but remains blank and does not time out. The funny thing is I only have this problem from some windows boxes. I can ping the address and get a response. I can also access several other Linux machines with no problems from these machines. I have done some goggle searching and talked to several administrators to no avail.
The Linux box is running Slackware with I believe Open ssh. The windows boxes are running WinXp sp1 and Putty 0.54; the same configuration as other boxes that work.
As far as I know there is know proxy sever. Both computers are part of the same domain at the school. There is no firewall to speak of and I can get access from home just not a couple a specific computers at school.
I've had a very similar problem with PuTTY the last few days. In fact, I've had a lot of network problems the last few days. Nautilus won't do any smb protocol, my syslogd daemon keeps stopping, and now this PuTTY problem, too.
Anyways, here is the setup.
My school gives each student storage space, so I have the PuTTY.exe on there, so I can ssh to my computer in my room from any computer on campus. This has always worked up until a few days ago. When I click "connect" (I think that is the button, can't remember, I think I actually just press enter), the connection (black terminal) screen opens for a few seconds (five or so), then it exits.
I have telnet, rlogin, insecure connections, etc disabled. Only Port 22 is open as far as remote command protocols go. I'm pretty sure my ssh daemon is still running, though I can't check on that right now.
ALL:.xxxxxx.edu (xxxxx is school's domain name)
There are only two reasons I can think of for this problem. (1) sshd has, for some reason, quit and needs to be restarted or (2) as of two days ago, the network no longer allows remote command protocols (which would be weird, and out of the blue, and piss off those in the Chem dept that run Chemistry computations on a Linux cluster via SSH/PuTTY).
I'll check on my ssh daemon later today. Also I'll check with the Chem Prof who admins the Linux cluster to see if he's had problems. Anyone else seen these problems?
Here's some more (hopefully useful) information on this problem.
I'm having the exact same problem with almost the same setup (I'm using Redhat 9). This problem started for me on a laptop that had an ip conflict with the Redhat server (yes, i fixed the ip conflict). Since then, the laptop won't connect with putty or the native xp ftp client. The server (a test server) has been re-formatted and re-loaded since the problem started and still the same results. This leads me to believe the problem is with the xp system (thanks, bill).
I also wiped out all of the registry entries and re-created profiles on the xp machine. I've tried host names and ip addresses. The putty log never shows more than the beginning time stamp.
I hate the thought of re-loading the laptop but until I get this figured out I actually have to get out of bed and work from my desk.
Anyway, I hope this gives the smart people a little more info to help figure this out.
I have the same problem with a Debian 3.0 Linux Server. This is a new installation, and I can't connect to it on SSH. Another anomaly is that if I try to view an HTMl page from that server, the page comes down but the images are not, only the first ~2000byte. If I refresh, than another ~2000byte.
I figure out: if I(on my XP) disable the Ethernet card, and enable it again, in the next ~10seconds I can connect in SSH to the server and the connection stay stable. But when I close the connection and want to connect again, theres only a big black window in PuTTY.
I'm on a UPC broadband, and from any other network the connection and the HTML works perfectly. I tried it on a laptop from the same network and it is not worked, so the problem is on the broadband I think.
I hope somebody (a Linux/NetWork guru) could figure out something from this...
Sorry to not respond for so long. I've been moving in at school.
Sounds to me like your SSH daemon isn't getting started when you boot. I've since switched to Slackware, but I believe you might try the following:
Go to your network settings. Find out where the settings are for services. There should be an option for SSH. If you check this option, the SSH daemon should start automatically when you boot. Under Slackware (and other distros that use the /etc/rc.d/rc.* convention) simply make rc.sshd executable (chmod +x /etc/rc.d/rc.sshd) and that should start up the SSH daemon automatically at boot.