secure connection to my home network

cokecan

cokecan

cokecan

Soldato
Joined
4 Jan 2004
Posts
7,774
Location
Nottingham
Hey Guys

I'm looking for some advice on setting up a secure connection to my home network from remote sites.

I have DNS Forwarding setup on my domain so it will forward a subdomain on to my modem's external IP.

I also have a few web services setup such as SABnzbd and Subsonic which are accessible over the net using the above subdomain and providing I use the correct port. The problem is these ports aren't always open or accessible from remote sites, plus I'd generally prefer a more secure connection for using remote desktop or similar. All the above are installed on my home fileserver that's running Windows Server 2K8 R2 and is behind a router running TomatoUSB.

What I would like to do is gain access to these services via a secure connection (SSH or VPN or similar) all down a single port (say 22 or 443 or something like that).

Is this possible to do? Ideally I'd like there to be little to no configuration needed on the client side as it's not always possible.

Thanks
 
MilanoChris said:
RDP?

I don't like services like Logmein as it's relying on a 3rd party.
Click to expand...

I wouldn't like to open RDP up to the cruel, cruel world that is the Internet. :eek:
But I agree about LogMeIn and similar - not 100% happy with connecting via any 3rd party in this day and age.
 
Thanks for the suggestions guys but I'd prefer not to have to use RDP/LogMeIn/Teamviewer or similar if all I want to do is use my Subsonic music streaming server for example. Also not keen on the idea of opening 3389 up for RDP unless there is an RDP gateway server or secure tunnel for it to connect down.

At the minute I just go to http://subdomain/music and I get my Subsonic server but this just uses port 80 and I'd like it to be down a secure tunnel if possible. Other things use different ports which arent always open on remote sites which was one of my main reason for wanting a single tunnel/route to my home network and then split off to the right service. Most of the places I generally want to use this stuff has port 22 open for SSH traffic
 
Opening up RDP to the Internet unnecessarily is just plain silly. ;)

VPN on port 443 is the way to go.
 
PistolPete said:
I wouldn't like to open RDP up to the cruel, cruel world that is the Internet. :eek:
But I agree about LogMeIn and similar - not 100% happy with connecting via any 3rd party in this day and age.
Click to expand...

What's the problem with enabling a port trigger for RDP? Mine has been like this since the dawn of time and has never been a problem. I RDP in from my phone and from work without issue.

Your router's firewall will keep things secure from prying eyes when you have port forwards set up anyway. GRC.COM to run the firewall test and notice that all are stealthed on a correctly set up router.
 
A port trigger is not the same as a port forward.

You may have had it set up for 2 years, that doesn't make it any more secure :)
 
Just set up VPN at home, guess I should have done it before but ah well.

I take it I'll just connect to it from my Mac/iPad whatever and then rdp to my PCs local IP or name?
 
You must log in or register to reply here.
Back
Top Bottom