Remote access my server from home over ADSL

P

PHTech

Senior Member
Joined
Aug 21, 2006
Messages
588
Reaction score
0
Location
Witbank
Hi there

I would appreciate it if someone can PLEASE help me setup a remote connection over ADSL from my home to my office. The ADSL routers that I am using are the following:

** Marconi Telkom Wi-Fi ADSL Router (4-port 10/100) -- At home
** ADSL Pots Router -- At Office

What I want to accomplish is that I want to connect remotely to my MAIN SERVER (Windows 2003 Server), establish a logon with a username and password so that I can work with my profile on the server, but display it at home.

I also tried to play around with the NAT and the port forwarding, but without any success. I also read about the DynDNS, but don't understand how to imply all those steps to create a successful remote connection.

I WOULD APPRECIATE IT IF SOMEONE COULD HELP ME ON THIS SITUATION WITH DETAILED STEPS (IF POSSIBLE). I HAVE PLAYED AROUND WITH THIS SITUATION, BUT WITH NO SUCCESS.

THANK U!
 
OK, i have not used either of those routers but its kinda simple.
Makes sure on ur 2003 box ur user has remote login rights, unless ur administrator. On your router you need to port forward port 3389 to ur servers ip address. Port 3389 is for remote desktop/terminal services. Make sure you havent blocked incoming traffic on ur 2003 box to port 3389 and you should have no problem. You only need to do the port forward on the router @ work.
 
Last edited:
Hamachi!

www.hamachi.cc

No-sweat VPN software - works like p2p and traverses most firewalls without fiddling. Definately recommended - you can operate any software as if you were on the same LAN.
 
I would stay away from hamachi until you learn how to configure ur network urself. Why run 2003 and not know how to remote desktop to it?
 
In my view, there are two decent ways of doing this.

1) VPN (You will essentially be on the same LAN as the server)
2) Direct Remote desktop/terminal services

I use the 1st option, but thats because it enables me to access not just the server, but all the other computers on its network.

For your needs, the 2nd option is probably best.

From what I have established, this is your setup.

Home computer - DSL Router -----------DSL Router - Work Server

To be able to control your work server from home, you are going to have to configure some port forwards on your *WORK* DSL Router. Presuming you know how to do port forwarding, all you have to do is forward the port 3389 (I hope dabouncer is correct, as I do not know the port myself) to your server's IP address.

Once this is done, you should be able to remotely access the server through terminal services or remote desktop.

Now you need a way to keep track of it's IP changes. DynDns is the way to do this. Create an account and add a "dynamic dns". (write down the hostname you choose)
Now move onto the support section of the page and download the update client. Install this client on your server and input into it your login details for the DynDNS site as well as the hostname you wrote down. I suggest you also select the "install as service" option to ensure it always gets started.

Once that is done, all is left is to input the hostname you wrote down into Remotely Desktop or Terminal Services, press connect and hope and pray it works!
 
Last edited:
right, listen up:

2003 server - you'll need 2 lan cards
1st lan card connects to your lan, give it an ip like 192.168.0.1
2nd card, crossover to your router, let it get an ip from dhcp
give your router an ip like 192.168.10.10. your router must dish out dhcp ip's, make the range of available ips 192.168.10.1 - 192.168.10.2, so theres only one available.

now, use Manage Your Server to setup Routing and Remote access. in the wizard select the option that allows remote access to your server. you can setup nat first if you need it for your work lan, which will share internet there from the 2003 box.

i'm not sure on your current routers, but on the netgear dg834g under Firewall Services make an inbound rule to always allow VPN PPTP protocol traffic on tcp port 1723 and bobs your uncle.
 
Last edited:
...I will try these options, thanx!

Hey.

Thanks for all the replies. I will try all those info you guys gave me!

Any other or more ideas welcome!

THANKS!
 
@riggs_9mmp - Not necessary for the 2 LAN card with different IP addresses. It works fine with 1 LAN card as long as your IP set is in the same range as the router IP Set. As for the rest if you are running 2003 VPN would be the best way to go.

To keep track of the IP changing create a DynDNS entry and download DynSite to dynamically update DynDNS everytime your connection gets rest.
 
@512Randburg - As far as I know, Routing and Remote access will not allow you to set up your server for VPN if the server does not have two network cards. During the configuration procedure it asks you for your WAN network card then your LAN. They cannot be the same card.
 
PHTech, is that ADSL Pots router not a USB modem? (I'm not too familiar with the different models, just remember that ugly white USB modem of Telkom has ADSL Pots written all over it...) If it is, then the USB modem will create a network connection (public IP) to which you can connect from home, no port forwarding required. Just need DynDNS to take care of the dynamic IP address (or just check the IP before you go home and hope it doesn't change soon ;) ). The internal network card will still be connected to the local network connection with private IP assigned. Once you are connected with remote desktop to the box on the public IP you can manage the server and access the the private network. Security may be an issue, so secure that public side on the box with a firewall to only allow remote desktop connections through.

If it is not a USB modem just ignore everything.:)
 
New router...

Hey.

Thanks again for the more replies!

I am going to take the ADSL pots router out, and replace it with a D-Link Wi-Fi ADSL router. (DSL-G604T). I will receive this router on 2006/08/24 and I have done some research on that router. To imply port forwarding and the DynDNS will be much more easier than that old POTS router.
 
Thanx...

Hey there,

Thanks for all the replies. I managed to setup my remote desktop successfully and it is working 100%. Thanks for everyone that contributed to my qeuery!
:D
 
Well riggs. Let me tell you how I managed to set it up firslty.

I got myself a new ADSL router (D-LINK DSL-G604T WiFi) and thats the first step that made my problem a little easier.

1. I went to a site, name www.PORTFORWARD.com, and they explained to me how to forward the 3389 (RDP) port on the D-link router.
2. I added LAN clients in my router and THEN setup the port forwarding.
3. Went to DynDNS and created accounts for a dynamic IP.
4. I went and added that information in the LAN clients page in my router.
5. THEN I STARTED HOPING AND PRAYING THAT IT WILL WORK (remember that its my first time I have worked with ADSL in such depth)

I started the 3G on my laptop, opened the Remote Desktop connection, and typed the hostname in the box, clicked connect (and with serious doubts if it was going to work), and suddenly I COULD CONTROL THE PC ON MY OFFICE NETWORK AS I WANT. What a relief.

Now, everyone who contributed to my post helped me, BUT the fact that you have such interest in who's help worked for me, I can say that u put it straight forward to me. I appreciate it.

THANX....
 
How's your server at the office connected? One network card with the router sitting somewhere on the LAN, or two network cards, one for router, one for LAN?

I still can't access my work server from a remote location, port forward and all... :(
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X