Port forwarding not working in dd-wrt

4

0

I just bought a Netgear (3700v4) wireless router to replace another one (3700v1) which failed. A friend had helped me get port forwarding working on the original one. One of the important things that it was doing was exposing Outlook Web Access. My laptop accessed it (Outlook using http access), and I could access it via a browser, and my cell phone accessed it. Now, none of those things works.

When I got the new router, other devices on my network connected automatically (DHCP), and it was pretty easy to set up wireless, but I can't get the port forwarding to work. All I did was add a few lines on the NAT screen:

enter image description here

Is there anything else I need to do? (I clicked Apply Changes, then later rebooted the router). How can I troubleshoot and fix this? It would sure be nice to have e-mail back on my phone and laptop!

UPDATE: By the way, I have Microsoft Small Business Server installed on my own server. That's where Exchange (OWA) is running.

Thanks for the help. Let me know any other info I can provide.

Thanks, Jay

birdus

Posted 2013-12-05T05:43:12.963

Reputation: 161

I use the "port range forwarding" tab, it's much more user-friendly – BlueRaja - Danny Pflughoeft – 2017-01-22T20:30:08.833

What you have done is how you port forward within DD-WRT. How do you know its not working? Are you sure the ip addresses are correct? – Ramhound – 2013-12-05T05:48:27.360

I used "ipconfig /all" to get the IP addresses for my server (for OWA and FTP) and my PC (for remote access). I know it's not working because my phone isn't retrieving e-mails and I can't use OWA. – birdus – 2013-12-05T06:03:41.260

So you are hosting OWA? – Ƭᴇcʜιᴇ007 – 2013-12-05T06:11:21.063

Yes. It's on my personal server. Let me clarify that in the question. – birdus – 2013-12-05T17:12:13.143

Could you test with yougetsignal.com (and test each port by filling it in and pressing Check) to see if the ports are really open?

– Rik – 2013-12-06T11:09:52.437

Answers

5

You need to fill the Source Net field. If you want all requests from no matter which host to be forwarded, that field should be:

   0.0.0.0/0

If instead you only want users from the site with IP address 1.2.3.4 to be properly re-directed, then you should fill the field with

   1.2.3.4/255.255.255.255

or, more simply,

   1.2.3.4

This is a picture of one of my routers' port forwarding page, working just fine:

enter image description here

MariusMatutiae

Posted 2013-12-05T05:43:12.963

Reputation: 41 321

I was having issues using 0.0.0.0, adding the /0 fixed it right up. Thanks. – user8675309 – 2019-08-17T00:27:17.117

My wireless router (the one with dd-wrt installed on it) plugs into my cable modem which has a static IP address. Should I use that IP or 0.0.0.0/0? I would like to be able to hit OWA, FTP, remote, etc., from any computer I happen to be using. – birdus – 2013-12-05T17:15:39.640

Then the correct way is to use 0.0.0.0/0 – MariusMatutiae – 2013-12-05T17:29:33.007

Great. I'll try it when I get home tonight. Will keep you posted. – birdus – 2013-12-05T17:54:17.290

2I added 0.0.0.0/0 to all three entries, then clicked Apply, then rebooted the router a while later. I still cannot access OWA (didn't try the other two). Any thoughts on how to troubleshoot this? – birdus – 2013-12-06T02:46:33.393

@birdus Have you tried from within your own network or from outside? Many routers prevent requests from LAN to go out and come back on the WAN side. – MariusMatutiae – 2013-12-06T07:02:56.523

Well, my laptop connects to my Exchange server via HTTP. That always worked before, but isn't now. It always worked no matter where I was, including from home. – birdus – 2013-12-06T14:43:24.057

Also, hitting just my domain name (which is mapped to the IP of my router—I guess I should verify that) doesn't work. That should hit my Small Business Server machine. Do I need to add another entry in the port forwarding for that? – birdus – 2013-12-06T17:13:44.703

@birdus I updated my post to include a picture of the Port Forwarding page in one of my routers. It works just fine. This makes me think there might different problems with your router. – MariusMatutiae – 2013-12-06T18:02:57.270

I just tried pinging my domain (home.birdus.com) and that doesn't work. I wouldn't have thought my static IP would have changed, but I guess I need to investigate that. – birdus – 2013-12-06T18:04:20.973

0

Somehow port forwarding doesnt work on my NetGear R7000. I had to manually enter this command under Administration > Commands in order to forward 8080 port...

iptables -t nat -I PREROUTING -p tcp --dport 8080 -d <WAN_IP> -j DNAT --to <LAN_IP>:8080

vipantonio

Posted 2013-12-05T05:43:12.963

Reputation: 1

0

I had the same issue with port forward but was able to fix it by assigning the port forward via command (CLI), I used the below syntax to get it working

iptables -t nat -I PREROUTING -p tcp --dport 80 -j DNAT --to 192.168.1.2:80 iptables -I FORWARD -p tcp -d 192.168.1.2 --dport 80 -j ACCEPT

Just change the ports & IP to suit your needs, also a reboot will clear this so you need to save startup to make it permanent.

Kassim Massop

Posted 2013-12-05T05:43:12.963

Reputation: 1