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 think this problem was more than 1000 times there and it was solved 999 times. But I tried everything which was posted in this forum, and its not working. My Problem: If I try to connect with putty to my new debian lenny server, there comes up the error: connection timed out.
The server is in the same network as my pc.
My router has a firewall, but i forwarded port 21 to the server ip.What else can i do?
Thank you that you try to help me.
Well now i configured it all on port 22 and forwarded port 22 in my router but its not working at all.
I can ping the server and can update the packages. I'm confused!
Your question is confusing. Is the traffic between the 'PC' (assuming you mean Windows host, here), and your Debian server traversing a router/firewall, or not? If yes, then what is the nature of said firewall/router? Have you established that a SSH server is actually running on the Debian server? To test this, on the Debian host:
If that succeeds, then we know the SSH server is running there. If not, then start it. Have you tried connecting from another host on the network? If not, then do so. What happens?
Are you able to connect to the Debian host in any other way: SMB, SFTP, telnet... etc. Does your 'PC' connect successfully to any other host? Any other host on the same network as the Debian host?
Please check all of these, and report your findings. Before a remedy can be suggested, the cause of the problem must first be determined.
Sorry, i think thats because my english is not that good as it could be.
1.The traffic between my pc(windows vista) and my server is traversing a fritz.box router with a firewall. But in the software-menu I forwarded port 21 to the server.
2. If i type in that command, its asking for my password, after typing in comes up:
Linux myhostname.mydoian.de 2.6.26-2-686 #1 SMP Mon Jun 21 05:58:44 UTC 2010 i 686
I think thats succsesfull, isnt't it?
3.I already tried to connect from another pc but it did not work. It also said connection timed out. I tried to connect to the debian server with telnet, also a timeout. 4. I have no chance to try to connect to a other server, because i have no acces to other servers. But i can use remotedesktop-connection, dunno if it matters.
Okay, it seems that there is a SSH server running on the Debian host. This is good.
You say that you have port-forwarded port 21 in the firewall, however this will not allow SSH traffic. You want port 22; port 21 is for FTP. I can only trust that you are capable of correctly configuring the firewall. Since other clients also seem to be blocked, it seems reasonable to suspect that the firewall is blocking the traffic. If you have root access on the Debian host, you could test to see if SSH traffic is reaching the NIC:
# As root:
# (substitute ethernet interface with eht1, eth2, etc. as appropriate)
# Do this while attempting to make a SSH connection from a client host.
tcpdump -i eth0 port 22
If this reveals that traffic is reaching your Debian host, then you should look into a local firewall issue on the Debian host. If no traffic arrives, then the firewall/router should be suspect. That you do have remote-desktop traffic passing through the firewall suggests that the firewall is functional. If the firewall is capable of dumping a table of it's rules, it may be useful to post those, here (in [CODE ][/CODE] tags, please).