Access lan over internet

L

leonb

Senior Member
Joined
Feb 2, 2005
Messages
665
Reaction score
157
Location
Durbanville
I want to access the routers on our lan remotely, i.e. when away and not connected on lan (e.g 3G). I have signed up for a dyndns name, and forwarded ports to the ip addresses on the lan. For example:

tftf.dyndns.org:3333 need to direct me to the web gui of the router with ip 192.168.1.1.

When I'm connected to the internet via our lan, this works perfectly. But using e.g. a 3G connection (or from work) to access it, doesn't work. I've tried disabling the router firewall, still does not work. Any ideas. I'm using a linksys wrt54g with dd-wrt firmware.
 
I assume you've set up your DynDNS on the wrt54?

Have you tried Teamviewer yet? It allows you to VPN into your network without much hassles.
 
ld13 said:
I assume you've set up your DynDNS on the wrt54?

Have you tried Teamviewer yet? It allows you to VPN into your network without much hassles.
Click to expand...

Hi. Yes, dyndns is set up. I can ping both the internet ip (current) and dyndns name from outside the lan.
 
There's a problem with your routing somewhere.
Make sure you are forwarding to the correct GUI port of the router you are trying to access.

If port 3333 is open on the ADSL modem, and forwarding to port 3333 on the Internal router, then it wont work unless port 3333 is your GUI port to access the router.

Understand?
 
Also remember the techies at work might block 3333 thinking it's for torrents
 
ben dover said:
There's a problem with your routing somewhere.
Make sure you are forwarding to the correct GUI port of the router you are trying to access.

If port 3333 is open on the ADSL modem, and forwarding to port 3333 on the Internal router, then it wont work unless port 3333 is your GUI port to access the router.

Understand?
Click to expand...


It is forwarded to the correct port. As stated earlier, when I'm using the internet connection from inside the lan, and I direct to tftf.dyndns.org:3333, it opens the correct gui (it is on port 80 - web interface). But when I'm on a internet connection outside the lan (e.g. on 3G), it will not direct to the gui.

I'm sure there are many experts around the forum that have encountered a similar problem?
 
Why not just setup VPN on your router so you can access the LAN directly.
Opening ports like that is dangerous.
dd-wrt supports L2TP openVPN if I am not mistaken, it is pretty easy to setup.
That would be alot safer and easier...
 
deepdiver said:
Why not just setup VPN on your router so you can access the LAN directly.
Opening ports like that is dangerous.
dd-wrt supports L2TP openVPN if I am not mistaken, it is pretty easy to setup.
That would be alot safer and easier...
Click to expand...

I only need to access some routers inside the network, and really want to set up VPN just for this - last resort only. I have a adsl modem in bridge mode connected to the router (wrt54G). Is it possible that, even in bridge mode, it could have a firewall enabled?
 
leonb said:
I only need to access some routers inside the network, and really want to set up VPN just for this - last resort only. I have a adsl modem in bridge mode connected to the router (wrt54G). Is it possible that, even in bridge mode, it could have a firewall enabled?
Click to expand...

Hi Leon, stupid Question but who is your ISP ?
 
If those routers don't use the same gateway you are connecthing through as their gateway no response will be received
 
PsyWulf said:
If those routers don't use the same gateway you are connecthing through as their gateway no response will be received
Click to expand...

Not entirely true, the router he connects through only need to know the route to the other router if it's on another network...

If he connects from the outside (to Dyndns IP) through a router with internal LAN IP of lets say 192.168.0.10/24 and the port forward has been setup to forward port 3333 to port 80 on IP 192.168.2.100/24 the router needs a route like 192.168.2.0/24 gw 192.168.0.200... if 192.168.0.200 is the gateway to the 192.168.2.0/24 range... but usually that should be there because if the route was not in then nothing would be able to access the internet on that 192.168.2.0/24 range....
 
ShawnStar said:
Not entirely true, the router he connects through only need to know the route to the other router if it's on another network...

If he connects from the outside (to Dyndns IP) through a router with internal LAN IP of lets say 192.168.0.10/24 and the port forward has been setup to forward port 3333 to port 80 on IP 192.168.2.100/24 the router needs a route like 192.168.2.0/24 gw 192.168.0.200... if 192.168.0.200 is the gateway to the 192.168.2.0/24 range... but usually that should be there because if the route was not in then nothing would be able to access the internet on that 192.168.2.0/24 range....
Click to expand...

I've seen stranger things in routing tables ;)
 
PsyWulf said:
If those routers don't use the same gateway you are connecthing through as their gateway no response will be received
Click to expand...


Same gateway, all computers on lan have access to internet through this gateway.

Why will it work perfectly from inside the lan, but not outside. Even inside the lan it has to connect to the dyndns host which gives it the internet ip to connect to? So it is not connecting from directly inside the lan.
 
Gateway would directly route a connection on it's public ip from any internal device internally if the gateway and the destination dyndns address are the same
 
PsyWulf said:
If those routers don't use the same gateway you are connecthing through as their gateway no response will be received
Click to expand...


Same gateway, all computers on lan have access to internet through this gateway.

Why will it work perfectly from inside the lan, but not outside. Even inside the lan it has to connect to the dyndns host which gives it the internet ip to connect to? So it is not connecting from directly inside the lan.
 
Have you tried setting up the Dyndns account on the main ADSL modem (DHCP server) and not the DD-WRT router inside the network...?
 
If I were you I'd ping the dyndns address from within the network ... sounds like it miiiight just be connected directly to the internal network IP and not the public IP.
 
ld13 said:
If I were you I'd ping the dyndns address from within the network ... sounds like it miiiight just be connected directly to the internal network IP and not the public IP.
Click to expand...

Give this a try and see what IP it resolves (should be a public IP of your internet router where you setup the portforward rules on)
If it works fine from inside the lan then the problem could only be with the port forward rules on the adsl/internet router... unless your isp is blocking incoming connections as well...
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X