This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
I am having a port forwarding issue with this router. I used to use a Pf Sense full blown BSD machine, but since the motherboard died in it, I had to get something up and running fast, and grabbed this router.
Netgear R6220
Firmware: V1.1.0.86_1.0.1
The following port forwarding works:
External 22 -> Internal 22 (192.168.2.217)
External 25 -> Internal 25 (192.168.2.3)
Etc.. If the external matches internal, it works
I'm now needing to forward non-matching ports, but they just will not work.
External 24203 -> Internal 22 (192.168.2.12)
External 24204 -> Internal 80 (192.168.2.12)
Reading other threads, I'll answer the most common questions that others have asked:
Yes, the one I want to reach is up and running, and can be reached by using internal IPs directly, on their respective ports of 22 and 80.
Has anyone else had issues like this on using mixed external / internal ports not working? On my old PfSense router, it worked as expected.
> [...] can be reached by using internal IPs directly, on their > respective ports of 22 and 80.
Should also work (from a system on your LAN) if you specify the router's WAN/Internet IP addesss and the appropriate external port number (verifying NAT loopback).
> Has anyone else had issues like this on using mixed external / > internal ports not working? [...]
Not I, but I don't have an R6220. I don't recall seeing any similar reports about any model. (Some older models didn't allow setting different int/ext ports, but that's a different question/defect.)
> Firmware: V1.1.0.86_1.0.1
Try something different/older?
> [...] grabbed this router. [...]
New, off a store shelf (or equivalent)?
Exercise the 90-day free support offer? Or the warranty?
>> [...] can be reached by using internal IPs directly, on their >> respective ports of 22 and 80.
>
>Should also work (from a system on your LAN) if you specify the >router's WAN/Internet IP addesss and the appropriate external port >number (verifying NAT loopback).
I agree that it should but does not.
>> Firmware: V1.1.0.86_1.0.1
>
>Try something different/older?
I honestly do not have the time to arbitrarilly pick an older firimware revision to test, and if it doesn't work, keep walking backwards.
>> [...] grabbed this router. [...]
> >New, off a store shelf (or equivalent)?
>
>Exercise the 90-day free support offer? Or the warranty?
The router is over 90 days from the date of purchase. Again, I can not afford much down time with this issue, since I work remotely. With this virus going around, I can't just easily go grab antother one off the shelf, or wait a week or two for a replacement.
On a side note though, while waiting for a reply, I do have another router exactly identical, that is on it's own network, and uplink etc.. (not related to this network) and it does have the mixed port forwarding, which does work, so I'm stumped on this one. I just got done going through every single setting between the two of them, and everything is identical in regards to NAT / WAN / LAN setups. Just different IPs on that network, and their respective port forwrds. The other router that does work, is the exact same model, and firmware revision.
