Port forwarding does not work properly, getting a ERR_CONNECTION_TIMED_OUT

[AEJ]

Port forwarding worked fine on my older Netgear router I have at my regular residence but now I am working from my childhood home and, although I did the exact same thing to port forward on the router there (set up port forwarding at Advanced Setup > Port Forwarding / Port Triggering) I am getting a "ERR_CONNECTION_TIMED_OUT" message. I can get to the local LAN server (http://192.168.1.13/) fine and trying to go to a port I have not opened results in "ERR_CONNECTION_REFUSED" so it is is probably a firewall issue or a bug. I have tried authorizing port 80, 443, 2377, 4789, 7946, and port 1880 to no success. I have also restarted the router several times to no affect. I came across a few other people with similar issues in my search for an answer but have not found a good response.

This has eaten up way too much work time!

My router is a R6400v2, not a R6400v1

[antinode]

> My router is a R6400v2, [...]

   Firmware version?  Connected to what?

> [...] my older Netgear router [...]

   Not a very detailed description of that device or its configuration.

> [...] although I did the exact same thing [...]

   It's nice that you're happy, but, with my weak psychic powers, I
can't see what you did at either site.

> [...] I am getting a "ERR_CONNECTION_TIMED_OUT" message. [...]

   When you do _what_, exactly?  From where?  As usual, showing actual
actions (commands) with their actual results (error messages, LED
indicators, ...) can be more helpful than vague descriptions or
interpretations.

> [...] I can get to the local LAN server (http://192.168.1.13/) fine
> and trying to go to a port I have not opened results in
> "ERR_CONNECTION_REFUSED" so it is is probably a firewall issue or a
> bug. [...]

   You're doing that from a system on your LAN?  So, we're talking about
some web server or other?  Running on a system of some type at
"192.168.1.13"?

> [...] I have tried authorizing port 80, 443, 2377, 4789, 7946, and
> port 1880 to no success. [...]

   Exhibiting the actual port-forwarding rules might be helpful.

> This has eaten up way too much work time!

   And you thought that providing a sloppy problem description would
spread the joy more evenly?

   For the usual problems with port forwarding, see:

      https://community.netgear.com/t5/x/x/m-p/1859106

   "1" is popular.  You seem to have covered "3".

[antinode]

> [...] You seem to have covered "3".

   The first part, at least.  But I don't recall seeing any complaints
about NAT loopback on the R6400v2, so I wouldn't expect problems with
that.