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.
because you pointed to NAT, the whole thing (pc-rooter-net-rooter-pc) was not clear to me. I was thinking more like this: rooter-rooter
schneidz, i can reach the fritz.box without problem. its at home so I did the connection and know the interface.
but the other rooter gives me trouble....there are too much people messing around it. since it is in a bar...
chrism01, when the prompt with my user-name is there i know we are OK
the problem was taht there was no prompt at beginning!
anyhow. when I can put my question clearly (explain WHAT operation I was doing) than we come back to subject.
ramkatral, my rooter is
FRITZ!Box Fon WLAN 7113 (UI)
i go in and out whenever i write the name of it in my browser and than identify myself with password.
since you show me the crucial mistake in my logic Im on a better way.
I was seing more the things like this
and the routers between as a part of the whole connection
now I see that the things are more
computer -router -net -router -computer
et essential is the connectin between ma computer and my rooter and the same is in the bar.
when I try to find to which PORT listens my SERVER
(I go to NETWORKTOOLS, than PORTSCAN and I put the address that DEVICE say is my computer uses to talk with the router)
Hire I have to see on right somewhere SERVER and on left the NUMBER of the Port. BUT all I see is this (the numbers of ports are changed):
port state service
5700 open unknown
38573 open unknown
57862 open unknown
I DONT KNOW WHICH OF THOSE PORTS IS THE ONE I NEED!!!
not able to figure out what the previous posts are trying to tell us.
from your home-pc type in ssh localhost and see if you can login. then see if you can login from another pc connected to the same wifi router.
ctrl-c to cancel... ssh is probably stuck trying to connect to your frizzy box (whatever that is).
ok. than slowly.
I try to find the TCP or UDP port my server listens on. when i know it i can write same number in my router and -did it!to check this i used this command:
ss -altnp | perl -ne '@_=split;printf"%-20s %s\n",@_[2,4]'
and I guess, I was expecting to see a port already with sshd server beside it.now i think I had to choose one of the open numbers and just put it in the router
now i will try to connect as you say. to do this Im installing on another laptop also ubuntu...
The Jinn is out of the bottle ! now, in this house, the time we spent benind the blue screen gets less and less....Ubuntu eats all machines around!
fritzbox is just a name of a product line of routers. I assumed ppl will understand I mean a classic home router -those the phone companies give you with one or two telphn numbers and internet.
yes, there are things that you have not heard of .its totaly ok
root@ubuntu:~# /usr/sbin/sshd -d
/etc/ssh/sshd_config: line 89: Bad configuration option: ps
/etc/ssh/sshd_config: line 90: Bad configuration option: exit
/etc/ssh/sshd_config: terminating, 2 bad configuration options
ANY IDEAS FROM HIRE ON ?
Last edited by enero forte; 09-07-2011 at 03:54 PM.
Ok; lets do one problem at a time, otherwise it'll ge tmessy.
First, assuming you want to use ssh, let's establish which box is the 'client' and which the 'server' eg
client(ssh) --> server (sshd)
ie client issue the ssh cmd (not sshd) to connect to server, which should be running sshd (d = daemon; server only)
client> ssh user@server_fully-qualified_domain-name
client> ssh firstname.lastname@example.org
Note that the server needs to have port 22 open on the firewall as sshd normally listens on port 22.
The client chooses a random outgoing port (>1023), so you can usually ignore firewall settings on client, as these are normally allowed.
To check firewall
on both systems.
Note also that if your server is not directly on the internet, but going through a router/modem, then you'll need to enable port forwarding on the router to fwd port 22 to the server for incoming cxns.
^ your sshd_config file probably got messed up... try commenting out those lines.
chris makes some great points.
lets start from the inside out.
in the first terminal run this:
sudo /etc/init.d/ssh stop
sudo sshd -d -d -d
# open another terminal window and type:
ssh -v -v -v localhost
copy and paste the output into your next post.
once that is working the next step would be to run:
ssh -v -v -v <internal-ip-address-of-server>
on another machine in your house.
the step after that would be to run:
ssh -v -v -v <ip-address-of-router>
from the bar.
That's what I keep trying to tell you. You are getting connection refused because your router is not forwarding the ssh request to the server. Nothing anyone here tells you will work until you tell your router to forward connections on port 22 to the server. That must be done first and formost. Once you do that you can ssh to the server to your heart's desire.
Edit: I just saw the part about the bad configuration file. I'm a hardware and networking kinda guy. I'll let these guys more knowledgeable with that part help.