Port forwarding to a router not working

G

GPSJane

Well-Known Member
Joined
Jun 14, 2009
Messages
482
Reaction score
1
Location
Johannesburg
I am using a Netgear DG834GT as a modem and a Buffalo Nfiniti with DD-WRT as a router. See picture.

I can access the Netgear modem remotely on the external ip (41.xxx.xxx.xxx) but I can't access anything else beyond it. I have set up port forwarding on the Netgear for every port and any user to the Buffalo ip 192.168.0.2 (for testing purposes) but I still can't access the Buffalo on any port.

Using port 8080 I get the Netgear admin page which is right but then how do I get another port, say 443, to show the Buffalo admin page?

I will also need to log in to other computers on the network, say 192.168.11.2, but for now I just want to fix the first issue.

attachment.php
 
An update:

First of all I can't access the Netgear admin page with port forwarding on, which means it is trying to forward but not succeeding.

Also, and I am sure this is a seperate issue but interesting none-the-less, I can't access the Netgear landing page via the ip address 41.xxx.xxx.xxx because Remote Access is turned off but I can access it via the host name I set up for Dynamic DNS. Since the host name is pointed to the ip address in question why would the Netgear allow that connection?
 
Can you show ur port forward page?

Does the netgear have some kind of ping ability, or does the buffalo?
Can you at least ping each other?

On the buffalo, in the access logs, can you see the port forwards hitting it?
Are there rules to allow access on the buffalo router for this access?


/EDIT/
On your port forward, do you have source:any port:81 (example) dstL192.168.0.2 port:8080 (assuming 8080 is the admin page?)
 
Last edited:
Hi, thanks for the reply.

The Netgear can ping the Buffalo. I can't ping from the Buffalo just yet.

There are no incoming connections logged on the Buffalo.

The Buffalo is set up to allow remote access.

Not sure what you mean but all ports are forwarded at the moment.

attachment.php

note: I have actually set only the AnyAll rule and not the HTTPS and SSH so there is no conflict.
 
Last edited:
It really feels like i am missing somethign simple here :(

The fact that with all ports forwarded:
1. u can still logon to the netgear from the external interface
2. no logs appear on the buffalo

The port forward is not doing anything at all.

I have to say, I dont like the port forward all ports thing...
Can you try do a single port forward?
Create a custom port number/service (make it 4000)
use this in the port forward rule

On another note, do you see this port forward in the netgear logs?
 
try hard resetting the router to defaults then port forward all agin, i had a problem once, did a hard reset and reconfigured everything from scratch. everything was fine after that
 
basically this :

buffalo router will have to have its gateway IP set to the netgear's internal IP.

Then

netgear will have to forward a port (443) to buffalo router's IP.
 
I did all that - tried a specific port - the reason I allowed all ports was just for testing.

BUT it turns out the hard reset worked because now I go straight to the Buffalo with the host name. (No port forwarding in use)

Now I have a problem; I can't access the Netgear from an external network.

What the ...?
 
GPSJane said:
I did all that - tried a specific port - the reason I allowed all ports was just for testing.

BUT it turns out the hard reset worked because now I go straight to the Buffalo with the host name. (No port forwarding in use)

Now I have a problem; I can't access the Netgear from an external network.

What the ...?
Click to expand...

Im confused, which hostname are you using to get to the buffalo?
You say port forwarding is completely off now?

It would make sense you cant reach the netgear, if all ports have been forwarded to the buffalo...
Seems like that netgear is dodgy....have you done a firmware upgrade?
 
I am using my hostname that I specified on the DDNS server.

Port forwarding for all incoming connections are blocked on the Netgear.

I didn't have a real internet connection other than the one the network is on so I hadn't checked from another ip but I did use a server test website and was given the all ok.

I think I was accessing the landing pages from inside the network even though using the external hostname. Because now connected on my cellphone I cannot access it. Which means the whole excercise was moot. Ok sorry that was silly.

So now the question is why can I not access my router (either of them) remotely even with remote access enabled and all DDNS settings correct?

/edit to add/
PS yes latest firmware
 
Last edited:
I would leave the DDNS out of this for now, get your current ip of the router and use that until you get things working.
There is a feature on the netgears to allow them to respond to pings on the external interface. Enable it. Ping it. Ping the DDNS name if you want, make sure its the same ip responding.

Lets go back to just accessing the netgear externally. Make sure logging is on.
When trying to access it from the outside (from a cellphone or 3G connection) do you see that in the logs?
Once we can confirm the traffic is getting to the netgear from the outside connection, we can move to remote access.

On remote access, what port does it use for the admin port? Are you browsing externally to the netgear using this admin port?
 
Ok, so after a hiatus during which I set up the rest of my network and dealt with various issues I am now back to this problem.

I am at square one; the graphic at the top is still valid and I can't access the router via the hostname (which points to the ip address 41.x.x.x) or the ip address 41.x.x.x.

I am doing this from an external network. The port is set to 8080. I have hard reset the router. There is nothing in the log at all and it is set to log access to web GUI.

Further from this I have set up the Netgear to forward https on port 443 to 192.168.0.2 (the Buffalo's WAN port) which may or may not be the right way but it does make sense to me! Although before I can figure out why this doesn't work I need to fix access to the Netgear.

/EDIT/ But I can ping the Netgear (at least I think it's the Netgear responding) from outside but this is not logged.
 
Last edited:
Progress! It turns out that even though Mweb says they have allowed incoming http and other traffic to your account they actually do not (typical bs) which means that I got it to work on other ports like 8245 (I read somewhere that I can use that port to bypass a proxy, not sure why though). So now on port 8245 I can access my Netgear router but I can't get it to forward properly to another ip on the network i.e. 192.168.0.2 - the second router.
 
Last edited:
GPSJane said:
Progress! It turns out that even though Mweb says they have allowed incoming http and other traffic to your account they actually do not (typical bs) which means that I got it to work on other ports like 8245 (I read somewhere that I can use that port to bypass a proxy, not sure why though). So now on port 8245 I can access my Netgear router but I can't get it to forward properly to another ip on the network i.e. 192.168.0.2 - the second router.
Click to expand...

I am almost certain i have port forwarded standard ports with mweb before.
Maybe they just dont like you ;)

The port forward should be pretty straight forward.
Create a custom tcp service for 8246,
set this to forward to the buffalo. Monitor in logs if it hits netgear, and if so if it hits the buffalo.

Now that you are getting traffic to your device, it should be downhill from here
 
As The_Librarian said, can you please confirm that the Buffalo device has the (internal) Netgear IP address as the default gateway?

Fault with this before and found that the gateway was not set or not set to correct to IP address.
 
One device to forward them all

@GPSJane

After your much earlier posts about "the one device" I see that the above devices are the ones you settled for.

( Could have gone I think for a simple basic modem only and a Wireless router with external HDD USB ? )

Anyway ..........

This may be completely all wrong and I have misunderstood everything :o

The difference between port forwarding and routing :confused:

I know on the netgear you can set up static routes ( and also use RIP V2 )

( There is a "private" and an "active" option ( Internal / External )


Would a static route from the Netgear to the Buffalo add anything to the mix ?

Now ( as I understand it ) ALL designated traffic from the netgear will flow to the buffalo ?

You can then just set up filters for the traffic that you want ?

Ignore and delete if nonsensical or not applicable ..........
 
MidnightWizard said:
@GPSJane

After your much earlier posts about "the one device" I see that the above devices are the ones you settled for.

( Could have gone I think for a simple basic modem only and a Wireless router with external HDD USB ? )

Anyway ..........

This may be completely all wrong and I have misunderstood everything :o

The difference between port forwarding and routing :confused:

I know on the netgear you can set up static routes ( and also use RIP V2 )

( There is a "private" and an "active" option ( Internal / External )


Would a static route from the Netgear to the Buffalo add anything to the mix ?

Now ( as I understand it ) ALL designated traffic from the netgear will flow to the buffalo ?

You can then just set up filters for the traffic that you want ?

Ignore and delete if nonsensical or not applicable ..........
Click to expand...

Since they are directly connected, I would assume the device would create a directly connected route.
This is an assumption though, its what almost every routing device does...doesnt mean this will though ;)
 
MidnightWizard said:
@GPSJane

After your much earlier posts about "the one device" I see that the above devices are the ones you settled for.

( Could have gone I think for a simple basic modem only and a Wireless router with external HDD USB ? )

Anyway ..........

This may be completely all wrong and I have misunderstood everything :o

The difference between port forwarding and routing :confused:

I know on the netgear you can set up static routes ( and also use RIP V2 )

( There is a "private" and an "active" option ( Internal / External )


Would a static route from the Netgear to the Buffalo add anything to the mix ?

Now ( as I understand it ) ALL designated traffic from the netgear will flow to the buffalo ?

You can then just set up filters for the traffic that you want ?

Ignore and delete if nonsensical or not applicable ..........
Click to expand...

@MidnightWizard I'm not sure what you're saying but I DO have a router, an ADSL modem and an attached Hdd.

I don't want static routes because I want to direct only some traffic to various destinations. I'm using firewall rules.
 
Opportunity

GPSJane said:
@MidnightWizard I'm not sure what you're saying but I DO have a router, an ADSL modem and an attached Hdd.
I don't want static routes because I want to direct only some traffic to various destinations. I'm using firewall rules.
Click to expand...

Bit OT -- but I see Incredible are having a Demo Stock Sale :D

Saw an all in one integrated Netgear DGN 2200 -- ADSL modem / WiFi / Switch / USB mass storage

At quite a good price. :erm:

There is also this one if you are feeling a bit flush --> Netgear DGND3700 Gigabit and Dual Band
 
Last edited:
Yeah I looked ta those. 3700 looked cool but expensive.

Anyway, I finally had success. A couple of hard resets and voila! It just started working. So I have forwards going to everything I need on the network. Thanks for all the help guys :)
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X