I think what its trying to do is take all traffic coming in from port 777 and send it internally to port 80. Is this what you want? _________________ WNDR3700 moved to openwrt
- my Wireless settings which (300 on 5.0) Wireless Config
7777 might be blocked by your provider as it is a know mallware port. It could be any number of things, for instance is your client (192.168.1.114) on a fixed IP address? If it is on a DHCP address it will fail at some point. Is this working on your own network?
If I create a port forward rule they all work, for instance I reroute external port 443 to internal port 22, no problems at all. There must be something on your end that is configured wrong or is blocked.
If you can give us more information we are happy to help.
Posted: Mon Dec 06, 2010 10:13 Post subject: Re: Port forwarding from Wan is not working. from Lan Works
blacardi wrote:
Seems to me that Port Forwarding from public IP Wan to lan is not working for WNDR3700. From Private IP Port Forwarding is working well.
Can anyone confirm this?
Wndr3700 r30 with DD-WRT 15437.
I have exactly the same problem. I want to forward 3389 (RDP) and another random port for a SSH server but the forwarding isn't working. I have an old WRT350N and it works flawless.
I read in the Netgear forum that this is a typical Netgear design issue ?!?
Can anyone confirm that ?
Posted: Tue Dec 07, 2010 7:14 Post subject: Re: Port forwarding from Wan is not working. from Lan Works
2q2 wrote:
blacardi wrote:
Seems to me that Port Forwarding from public IP Wan to lan is not working for WNDR3700. From Private IP Port Forwarding is working well.
Can anyone confirm this?
Wndr3700 r30 with DD-WRT 15437.
I have exactly the same problem. I want to forward 3389 (RDP) and another random port for a SSH server but the forwarding isn't working. I have an old WRT350N and it works flawless.
I read in the Netgear forum that this is a typical Netgear design issue ?!?
Can anyone confirm that ?
I just set this up today on my WNDR3700 and build 15778. It works fine for me with RDP.
I've got the exact same problem. I'm pretty sure all of us aren't "doing something wrong". I tried everything I could think of, and no, my ISP does not block the port forwarding for these ports as I was able to forward them before... I tried using single port forwarding of, for example, port 80 to internal 192.168.1.115:80. My exact settings across the line were: Http | Both | 255.255.255.255 | 80 | 192.168.1.115 | 80 | enabled checked. In this scenario, visiting my WAN IP gave me the DD-WRT admin panel!?!? .. For Port Range Forwarding, I got nothing for any ports I tried. Even DMZ does not appear to be working. Not sure what's going on here but it seems to be a legit problem. Unless there is some other contingent setting that must be on and/or off, the port forwarding is definitely not working for me. Any help is greatly appreciated.
It will not forward any port (saving, applying and rebooting as the ultimate IT fix ). Now I did notice there was a new field for source filtering which was empty. Did not try to put in 0.0.0.0/24 to let the evil interwebs in as I presumed it would do that by default.
It's not mentioned in the online help file as a mandatory field. One would expect it at least to be pre-filled then. Long story short, I didn't think I was doing anything wrong :)
Anyway, I'm not in the position to try this again at the moment to see if it makes any difference.
If it doesn't help I guess it's more likely to be a build issue in that case.
). Now I did notice there was a new field for source filtering which was empty. Did not try to put in 0.0.0.0/24 to let the evil interwebs in as I presumed it would do that by default.