× We are aware of an issue affecting Nighthawk CAX30 Cable Modem Routers that may have resulted in an interruption of internet service. For instructions to restore Internet connectivity click here.
Reply

Re: Portforwarding not working on a D7000 Nighthawk

BennyF2k20
Aspirant

Portforwarding not working on a D7000 Nighthawk

Hey guys, I really hope someone can shed some light for me here, I've spent the past 2 days researching and trying to get portforwarding to work, even bought a new modem incase that was the issue and for some reason no matter how hard I try I can't get it to work.

 

I'm trying to setup an old i7 6700k pc I have as a game server to host Space Engineers and a race sim lobby or 2, but I can't even get as far as getting port forwarding set up for space engineers. I'm using a Netgear nighthawk D7000 modem/router now, was using a Huawei HG659 and neither of them seem to of been able to port forward so I'm now guessing it's either an issue in my server PC or on TPG's end.

 

I've set a static IP to my server PC being 192.168.0.112 (it was x.x.0.3 but I changed it to see if it'd work, it didnt) a subnet mask of 255.255.255.0 and the gateway/DNS servers set to my gateway IP of 192.168.0.1. I've got outbound and inbound rules for both the Torch server software & the ports to ensure nothing gets blocked. I've tried ports 5555, 27016, 26017 as well as disabling firewalls entirely on the server PC.

 

In the modem I've gone in and set port forwarding custom services to allow the port (currently 27016), using same external and internal port and directing it to the server PC's static local IP (192.168.0.112) and tried setting it to both TCP/UDP & just UDP (Space Engineers uses UDP).

 

I also setup DDNS but not using that yet manually getting my IP and checking that way as well as using NMap to check open ports as well as trying to connect to the server via direct connect in-game. I can confirm the server is working great locally as I can connect via my local IP (192.168.0.112:27016) but I can't for the life of me connect via my public IP. Server settings are 0.0.0.0:27016 and tried 192.168.0.112:27016 as well)

 

Now, I do have one concern, my modem's subnet mask is 255.255.255.255 but I even tried setting my server PC's subnet mask to this and got nowhere still so changed it back.

 

Please help me, I just want to play some space engineers in my spare time but right now I'm spending all my spare time trying to do something I feel like I know how to do. I've portforwarded many times in the past and never ever run into this much issue.

Also checked that my internet IP address on the modem matches my internet IP address on whatismyip and it does so seems there's no other server interfearing.

 

Only the netgear d7000 acting as a modem/router, no external router or AP attached.

Modem: Nedgear Nighthawk D7000 V1.0.0.62_1.0.1
ISP: TPG
OS: Win10 Pro
VDSL2 NBN FTTN

Message 1 of 6
antinode
Guru

Re: Portforwarding not working on a D7000 Nighthawk

> Modem: Nedgear Nighthawk D7000 V1.0.0.62_1.0.1

 

   So, that's a D7000v2, not a D7000[v1]?  Look for "Model" on the
product label.

 

> I've set a static IP to my server PC being 192.168.0.112 [...]

 

   Terminology: A "static" address is configured on the device itself.
What you configure on a (DHCP server on a) router is a reserved dynamic
address, not a static address.  Either should fix the server's LAN
IP address, which is what you need for port forwarding, but using a real
static address can cause trouble if that address is still in the DHCP
pool.

 

> [...] I can't for the life of me connect via my public IP. [...]

 

   Are you trying to do that from a system on your LAN, or from the
outside world?  D7000v2 firmware is buggy enough that "NAT loopback"
doesn't work, which can defeat attempts to use its WAN/Internet address
from its LAN side.


> Now, I do have one concern, my modem's subnet mask is 255.255.255.255
> [...]

 

   Your router has two independent network interfaces, LAN and
WAN/Internet; each has its own address, subnet mask, et c.  The
WAN/Internet stuff must agree with your ISP.  The LAN stuff you can play
with.

 

   For the usual problems with this stuff, see:

 

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

 

But you seem to have covered about everything.  Except the lame D7000v2
firmware and its broken/missing NAT loopback, of course.

Message 2 of 6
BennyF2k20
Aspirant

Re: Portforwarding not working on a D7000 Nighthawk

Yeah V2, Sorry forgot to add that.

By Local statuc IP I mean I setup a local IP on the windows machine that wont change so it'll always be 192.168.0.112 for the modem.

I'm trying to connect via my public IP via direct connect to check server status as well as using NMap to check ports. CMD shows the port in use but NMap does not.

When connecting via LAN (192.168.0.112:27016) everything works as expected and it's fine. The issue comes when trying to connect to it from my public IP. It also does not show in the online servers menu in-game, only my LAN menu.

I've never taken more than an hour to portforward before, Idk if I've forgotten something with lack of practice but I'm baffled. Everything is on the right subnet mask (24) and it seems that the servers working as expected when connecting via the IP so the issue has to be either in my port forward or something else.

Message 3 of 6
antinode
Guru

Re: Portforwarding not working on a D7000 Nighthawk

> By Local statuc IP I mean I setup a local IP on the windows machine
> that wont change [...]

 

   That's static.  The potential problem is that the DHCP server on your
router doesn't know about it, and might be willing to issue that address
to some other client device.  The fix is to shrink the DHCP pool, and
use only non-pool addresses as static addresses.

 

   For example, on a typical Netgear router, the default DHCP pool range
is ".2" - ".254".  (ADVANCED > Setup > LAN Setup : Starting IP Address
and Ending IP Address, or similar.)  That is, the whole usable address
range, except for the router itself (".1").  If you shrank that to, say,
".2" - ".99", then you could use the range ".100" - ".254" for static
addresses, and there would be no chance of the DHCP server in the router
granting any of those non-pool addresses to any DHCP client device.
(Barring router firmware bugs, of course.)  I'd probably use ".2" -
".199", for the pool, leaving more pool space, but then you'd need to
change the address of your server, and, hence, the port-forwarding rule.


> I'm trying to connect via my public IP [...]

 

   That's not new information, and doesn't answer the critical question:

 

>    Are you trying to do that from a system on your LAN, or from the
> outside world? [...]

 

   If you use the router's WAN/Internet address from its LAN side, then
the router needs to handle that in a special way.  The feature is called
"NAT loopback" (among other things), and, as explained above, that
feature is broken/missing in the firmware for a D7000v2.

 

> I've never taken more than an hour to portforward before, [...]

 

   Using a router where NAT loopback works helps.

 

   Because of this defect in the D7000v2 firmware, tests using the
router's WAN/Internet address from its LAN will fail.  If everything
(else) is right, then a test from the outside world should work.

Message 4 of 6
BennyF2k20
Aspirant

Re: Portforwarding not working on a D7000 Nighthawk

So finally managed to get someone else to try and connect for me who wasn't busy, and sure enough. It was the loopback issue! Thank you heaps my man! Little frustrated and annoyed with the amount of time I spent trying to fix an issue that was likely working. I just found it weird NMap and the servers public server list wouldn't show me the server either.

Now I just need to solve a new found issue that Space Engineers doesn't let you type a HTTP URL into it's server IP connect field so need to find another way of either connecting to the dynamic IP or getting my host to give me a static IP if they do/will, don't like that idea as much though.

 

Message 5 of 6
antinode
Guru

Re: Portforwarding not working on a D7000 Nighthawk

> [...] sure enough [...]

 

   Glad to hear that you got it working (as well as possible with the
defective firmware).

 

> [...] Space Engineers doesn't let you type a HTTP URL into it's server
> IP connect field [...]

 

   You lost me there, but it sounds like a non-router problem.

Message 6 of 6
Top Contributors
Discussion stats
  • 5 replies
  • 1807 views
  • 0 kudos
  • 2 in conversation
Announcements

Orbi WiFi 6E