connectng to ubuntu server with putty from another house

S

scudno1

Member
My Satellite Setup
dm800s nabilo blk hole 0.12
28.2e,13e,16e,19.2e
dm500s pli jade
80cm dish and motor
My Location
glasgow
hi all im really lost i have a ubuntu server in my dads house and i am trying to speak to the server with putty from my own house but not haveing any luck i have tried to connect to it with my host name but doesnt seem to work,when im in my dads house and i use my internal ip of the server i connect no problem but when i try from my own house i cant, has anyone else came across this problem,any help would be great.
 
Hi @scudno1,

While connecting remotely (via internet not LAN) you will need to use SSH for security. Presumably while connecting Locally via LAN, you are just using the standard FTP Port of 21 but to use this over the internet remotely is far too much of a security threat.

The Ubuntu Server will need to have SSH running and 'Listening' on the SSH Port you have chosen. Also, the router at your Dad's house will need to have Port Forwarding enabled for the chosen SSH port (DO NOT use the standard SSH Port of 22 but something high and obscure).

Here's a thread asking about remote ftp, including how I setup SSH/Dropbear on my DM7000S:
http://www.satellites.co.uk/forums/...72686-remotely-login-dreambox.html#post919894

It should be much easier on an Ubuntu server as full SSH will be built in. Wherever my post mentions my Asus laptop, this will be your remote PC. Where I mention my DM7000S, will be the Ubuntu server at your Dad's but will use SSH and not Dropbear.

Hope some of this helps.

Best wishes, John.
 
I would strongly recommend that you don't open a command window to the internet. This creates a window of opurtunity for hackers, even when using putty/SSH. The problem is that once they get in on this interface your Ubuntu is their oyster and could be the goose that lays the golden eggs (depending on what you have on your LAN. SO if you decide to do it, be aware of the dangers.
 
shumifan50 said:
I would strongly recommend that you don't open a command window to the internet. This creates a window of opurtunity for hackers, even when using putty/SSH. The problem is that once they get in on this interface your Ubuntu is their oyster and could be the goose that lays the golden eggs (depending on what you have on your LAN. SO if you decide to do it, be aware of the dangers.
Click to expand...

I don't really understand what you're saying here? You wouldn't open a "command windows". You would need to open an SSH port (TCP port 22 or chane as mentioned above) on your internet router/firewall and also create a redirect rule or forwarding rule to the SSH Host. E.G. First, you need to get the external IP address of your Dad's internet connection. This can be done by going to _http://www.whatismyipaddress.com from a PC in you Dad's house. Lets say the external address comes back as, 1.1.1.1. You will then need to configure your Dad's router to allow TCP access on port 22 and forward it to the internal IP address of the Ubuntu server. Then from your house, you point putty at 1.1.1.1 and it will connect to your Dad's router where it will passed on to the Ubuntu box.

As mentioned above I wouldn't recommend using TCP port 22 on the Ubuntu box and I would recommend disabling PasswordAuthentication on the ssh server and configuring Key authentication. Also, there may be a problem with your Dad's external IP address changing every so often, to get around this you can either use a DynamicDNS service or configure the Ubuntu to run a daily cronjob with a script to get your external address then mail to you.
 
Hi all,

I agree fully with you @packetstormer.
RSA key validation, disable password login, obscure port number and I really see very little chance of being hacked!
Most of the hackers try the standard port numbers 21, 22, 23, 80 and the like. Since moving to an obscure high numbered port, they don't even know I'm there! I have not had one single attempted hack since I moved to a high port number. Initially I ran my SSH (for about 1 day!) on port 22. Nobody got in because of RSA key validation and disabled password login. However, my router log was full of attempted hacks! It was about one attempt every 10 seconds!
Since moving to a high (above 1024, up to 65535) port number there have been NO attempted hacks!

Before SSH, I had ports open and they did successfully crack my password and FTP & Telnet into my DM7000S!!
However, once there they did not know what to do as it was a Dreambox.....and, of course, they were looking for some nice juicy Bank Details!

Best wishes, John.
 
@packetstormer: I used the term 'command window' as it is a familiar term to Windows users whereas a putty or telnet session is not. When I look at the question raised I think there is a high risk of scudno1 not securing the connection properly (if port forwarding and DDNS etc is not even understood).
 
Back
Top