Can't connect from one Ubuntu notebook to another Ubuntu notebook via SSH

[khurtsiya]

any suggestions?

[steeldriver]

You may have better luck putting the server on the home wifi network and trying with the client connected via your 3G service - not forgetting to set up the appropriate port forwarding on your home router of course

[khurtsiya]

is there a way to do this without port forwarding?
and what if server is moving and sending me actual IP - can't I connect to it, assuming SSH is configured and I have password?

[The Cog]

any suggestions?

Try pinging the server to see if there is any basic network connectivity.

[wlraider70]

Can you give us the output of ifconfig

[fosterD]

There are two things you can try:
1- SSH server and client are running fine
2- The connectivity between your home laptop and remote laptop (using 3G)

I suggest that you should connect both laptops into a private network (your home network, e.g 192.168.0.x)
Suppose your remote laptop's ip address in 192.168.0.10

ssh <remote-user>@192.168.0.10

By default, ssh uses port 22, if it is configured to use another port number, you can use '-p <port-number>'
At this stage, you can confirm that ssh is running fine

Then you can try to use external ip address

- Make sure your external ip address (3G) is correct (https://www.google.com.au/#q=what+is+my+ip+address). It should be pingable.
- You need to configure your home router to forward ssh packets (port 22) from external to your home laptop. Configuring port forwarding is an easier approach here.

Hope this could help

[khurtsiya]

Hi! Finally connection established, thanks to this short and clear article: http://linuxwave.blogspot.com/2008/0...se-tunnel.html

But! Now I have this error:

~$ ssh -vvvv k@91.111.136.30 -p 7777
k@91.111.136.30's password:
debug3: packet_send2: adding 64 (len 52 padlen 12 extra_pad 64)
debug2: we sent a password packet, wait for reply
debug1: Authentications that can continue: publickey,password
Permission denied, please try again.

Looked many other articles with this problem and fotums, but none of the solutions helped. Any suggestions much appreciated.

[khurtsiya]

Here is the instruction from that article:

1. Create a tunnel from middle to target and leave it open when you are still at the office. You cn also ask your colleague at the office to do this. The below command will open port 12000 on middle for listening and forward all request on port 12000 on middle to port 22 of target

user@target $ ssh -R 12000:localhost:22 middleuser@middle

2. Now you can access to port 12000 on middle from current and you will be forwarded to port 22 on target

user@current $ ssh targetuser@middle -p 12000

3. If somehow you cannot access, access middle first, then connect to port 12000 of localhost

user@current $ ssh middleuser@middle
user@middle $ ssh targetuser@localhost -p 12000

You are now in the target server