Reply

Port forwarding stopped working on R7000

seandr
Follower

Port forwarding stopped working on R7000

I have two Nighthawk R7000 routers, one at home and the other in my office, both running latest firmware V1.0.9.88_10.2.88. Both have been configured to route port 3389 to desktop computers connected to them with ethernet cables for Remote Desktop Access. It had been working great for a long time, but then a month or so ago they both stopped working. 

 

I have verified that I can Remote Desktop from other computers connected to the same router using local private IPs. However, when I use the public IP, I can not connect.

 

Any ideas? Was this broken by the latest firmware update?

 

Thanks.

Model: R7000|AC1900 Smart WIFI Router
Message 1 of 2
antinode
Guru

Re: Port forwarding stopped working on R7000

> I have two Nighthawk R7000 routers, [...]

 

   Connected to what?  Some kind of modem?  ISP?

 

> [...] Both have been configured to route port 3389 to desktop
> computers connected to them [...]

 

   "configured" how, exactly?  Are you talking about port forwarding?
(Routing is an actual technical term, which refers to something else.)
If so, then what are the actual port-forwarding rules?  Copy+paste is
your friend.  What are the (LAN) IP addresses of these Windows systems?
Do those addresses agree with the addresses in the port-forwarding
rules?

 

> I have verified that I can Remote Desktop from other computers
> connected to the same router using local private IPs. [...]

 

   Ok.

 

> [...] However, when I use the public IP, I can not connect.


   Actual error message?  Is that still from a system on your LAN, or
from the outside world?  Ideally, both should work, and you could test
both, but which way were you testing?  (Try the other way?)


   Does the IP address of the WAN/Internet interface of the R7000 agree
with the public IP address which you specify when you're trying to make
the Remote Desktop connection?  ADVANCED > ADVANCED Home : Internet Port
: Internet IP Address?

 

> [...] Was this broken by the latest firmware update?

 

   I doubt it.  I know nothing, but I'd expect to have seen more such
complaints, if so.

 

   The usual problems with this stuff are:

 

   1. Wrong external IP address (different from the port-forwarding
router's WAN/Internet IP address).  (An intermediate NAT router, for
example, could cause this.  Or an ISP using carrier-grade NAT to
conserve IPv4 addresses.)

 

   2. Bad port-forwarding rule (wrong port(s), wrong target address --
including a wandering target).


   3. Server not listening on the port-forwarding target system.

 

   If you can connect locally, then that should not be the problem.

 

   4. External influences: ISP blocking, other firewalls, ...


   Or, of course, faulty firmware.  If that's your suspect, then you
should be able to revert to older firmware.  Visit
http://netgear.com/support , put in your model number, and look for
Downloads.  (For older versions, under Firmware and Software Downloads,
look for "View Previous Versions".)  Find the kit(s).  Download the
kit(s) you want.  Read the "Release Notes" file for instructions.

   From what I've read here, V1.0.9.42_10.2.44 seems to be the last
version which met with wide approval.

Message 2 of 2
Top Contributors
Discussion stats
  • 1 reply
  • 492 views
  • 0 kudos
  • 2 in conversation
Announcements