NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

GuliG's avatar
GuliG
Aspirant
May 29, 2021

Port Forwarding on a D7000 not working

I'm a networking novice: please be patient. I've looked at several similar threads (1960181, 1517696, 1556128, etc) for this device and other modems/routers and have been unable to resolve my issue....
antinode's avatar
antinode
Guru
May 29, 2021

> I've looked at several similar threads [...]

 

   Not the best examples, I'd say.  The D7000v2 has its own problem in
this field (no NAT loopback), so discussions of that model can mislead a
D7000[v1] user.

 

> I'm trying to open a handful of ports (80, 8080, 8085, 7878...) [...]

 

   Why?  You're running a web server?  And what else?

 

> [...] Below is my forwarding configuration within the modem.

 

   I can't (yet) see your picture.  In-line images must be approved
by a moderator before others can see them.  The time required varies.
Attachments have no such limitation.  Of course, attachments have their
own one-per-message limitation.  In the mean time, copy+paste is your
friend.

 

> My ISP is Centurylink. [...]


   You have DSL service?

 

> This is a D7000 (v1? [...]

 

   A D7000v2 should say "D7000v2" under "Model" on its product label.

 

> [...] with Firmware v1.0.1.78_1.0.1.

 

   That's a D7000[v1] firmware version.

 

   D7000[v1] firmware is far from bug-free, but, so far as I know, its
port forwarding works.  (I currently have about 16 port-forwarding rules
configured on mine.  Which is also running V1.0.1.78_1.0.1, with
(resold) CenturyLink (old. slow) DSL service.)

 

> Turned on/off the UPnP as suggested in another thread, but again don't
> know enough to know what that changes.


   Sounds good to me.  It should prevent the router from trying to do
automatically what you're trying to do manually.

 

   For the usual problems with port forwarding, see:

 

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

  • GuliG's avatar
    GuliG
    Aspirant
    May 29, 2021

    Thank you for the response, antinode. 


    "> Why? You're running a web server? And what else?"
    It's a private game server for an old MMO which includes web-based account creation system. I'm following a guide for that process but am stuck on getting the necessary ports opened, everything else appears to work fine. 


    "> I can't (yet) see your picture. "
    Sorry, I was unaware of that limitation. I've included an image with a few screenshots together. The port forwarding configuration is obviously marked #1 in the attachment, the other marked bits are mentioned later in this post. Transcribed example:

     #Service NameService TypeExternal Starting PortInternal Starting PortServer IP Address
    1W80TCP/UDP80-8080-80192.168.0.111

     


    "> D7000[v1] firmware is far from bug-free, but, so far as I know, its port forwarding works.  (I currently have about 16 port-forwarding rules configured on mine.  Which is also running V1.0.1.78_1.0.1, with (resold) CenturyLink (old. slow) DSL service.)"
    Very relevant experience then, I'm glad you reached out! Yes, it's DSL service and since the v1 is capable, I'm sure it's user error in some capacity, I just don't know where I would've messed things up. 

     

    "> For the usual problems with port forwarding, see: https://community.netgear.com/t5/x/x/m-p/1859106"
    I've read through the thread, so here are a couple additional points of information and questions.

    • I don't think I'm using an intermediate NAT router. The D7000 is my only modem/router and the host computer is connected directly to it with ethernet. 
    • The Internet IP Address listed in Advanced>Advanced Home is the same IP that is returned when using WhatIsMyIP. 
    • I've made sure the system always has the right address using (I think) static configuration and reserving an IP outside the DHCP range. The IPv4 address I see on the host when using /ipconfig and when looking at the list of wired devices in Advanced>Attached Devices shows the IP that I reserved (attached #2).
    • I'm frankly not sure how to "access the server from a system on your LAN using the server's LAN IP address" so I had to search around. Is it just a matter of entering 192.168.0.111:80 (tried with and without the port) in the browser address bar of another computer on the network? When I do this, I receive a message indicating the address refused to connect (attached #3). 


    Thank you again.

    • antinode's avatar
      antinode
      Guru
      May 29, 2021

      > [...] I'm following a guide [...]

       

         Thanks for the helpful link.

       

      > o The Internet IP Address listed in Advanced>Advanced Home is the same
      > IP that is returned when using WhatIsMyIP.

       

         That clears usual problem 1.

       

         The port-forwarding rules look plausible (if you want those ports).

       

      > [...] Is it just a matter of entering 192.168.0.111:80 [...]

       

         "http:192.168.0.111", with or without ":80".  A modern browser might
      default to "https:192.168.0.111", which implies ":443".

       

      > [...] refused to connect [...]


         Welcome to usual problem 3.  "Connection refused" normally means that
      you've reached the destination system, but no one there is listening at
      the specified port.  And, as it says, "If you can't access the server
      locally, then there may be little chance of doing it from the outside
      world."

       

         Knowing nothing about your game server, I can't tell you if you're
      not running it correctly, or if it's not working for some other reason.
      Do the ports other than 80 do anything different?