NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Nighthawk R7960P Portforwarding Issues
Model: R7960P Nighthawk X6S AC3600 Tri-Band WiFi Router I have a gateway (modem/router) from my ISP set to bridge mode and connected to my Netgear Nighthawk router. I have created a reserved IP ...
> Currently I am only trying to run one server on my own computer. I
> have never run multiple at the same time.> [...] I am specifying a non-default port number for each Minecraft
> server that I create within the Minecraft Server Properties folder. As
> stated above, I don't run multiple at a time and I run these servers on
> one computer.Ok. So, then, why would you use a non-default port number for this
one server?> Its rules are as follows:
That's one rule, but ok. Is there a server running on the system at
"192.168.1.200", listening at port ("query.port", I gather) "25585"?> To me, "the server address" means the IP address used to join a
> Minecraft server. [...]
Sadly, that's ambiguous. From the outside world, you'd need to use
your router's WAN/Internet address (which is your public IP address).
On your LAN, you can use the server's LAN IP address. Or (if NAT
loopback is working), you could also use your router's WAN/Internet
address from within your LAN.> [...] "My internal IP address" means my computers reserved IP address
> as stated within my R7960P router. [...]If you mean your computer's (LAN) IP address, then say that. "My" is
not a useful description of an IP address, unless _you_ have an IP
address.> [...] created one reserved IP address for my own computer, [...]
And what is that address reservation?
> [...] which is the internal IP address shown above within the one
> port-forwarding rule I have. [...]
Wouldn't it have been easier, as well as clearer, to say something
like "192.168.1.200, as in the port-forwarding rule shown above"?And is that computer really at that address?
> So I don't need to use static addresses then, assuming I have
> correctly set up my address reservation? (just to be clear)Right. So long as the server system has the IP address specified in
the port-forwarding rule, it doesn't matter how you managed that.> [...] Assuming I did the port-forwarding rules correctly, I should be
> telling all incoming requests to join my specific computer at
> 192.168.1.200 through the port number that I specified, right?"I"? The rule in the router should.
If your server is running on the system at "192.168.1.200", listening
at port "25585" (whyever), then you should be able to connect to it
("join") from a system on your LAN by specifying that address and port
(often written as "192.168.1.200:25585").If your port-forwarding rule is correct (and NAT loopback is
working), then you should also be able to connect to it from a system
on your LAN by specifying the router's WAN/Internet IP address (your
public IP address) and (with your external=internal p-f rule) that same
port number. And anyone in the outside world should also be able to
connect to it by specifying that same public-address+port combination.
What could go wrong?
> Does that mean that you're running multiple Minecraft servers? All
> on one computer, or all on different computers, or what/where?
Currently I am only trying to run one server on my own computer. I have never run multiple at the same time.
> How are those servers configured? (What's in one of your "multiple
> Minecraft server files"?) What are the corresponding port-forwarding
> rules for each active server?
As an example, one old server I haven't run in awhile looks like this inside of its Server Properties folder. It is not an active server, however. I don't have any port-forwarding rules set up for it.
#Minecraft server properties #Wed Jun 05 17:10:06 PDT 2019 spawn-protection=16 max-tick-time=60000 query.port=25571 generator-settings= force-gamemode=false allow-nether=true enforce-whitelist=false gamemode=survival broadcast-console-to-ops=true enable-query=false player-idle-timeout=0 difficulty=easy spawn-monsters=true broadcast-rcon-to-ops=true op-permission-level=4 pvp=true snooper-enabled=true level-type=default hardcore=false enable-command-block=false max-players=20 network-compression-threshold=256 resource-pack-sha1= max-world-size=29999984 rcon.port=25575 server-port=25571 server-ip= spawn-npcs=true allow-flight=false level-name=world view-distance=10 resource-pack= spawn-animals=true white-list=false rcon.password= generate-structures=true online-mode=true max-build-height=256 level-seed= prevent-proxy-connections=false use-native-transport=true motd=A Minecraft Server enable-rcon=false
I do have one port-forwarding rule set up for another server. Its rules are as follows:
Type External Starting Port External Ending Port Internal Starting Port
TCP+UDP 25585 25585 25585
Internal Ending Port Internal IP Address
25585 192.168.1.200 > I don't know what "the server address" or "my internal IP address"
> means to you. _Which_ "the server"? _You_ don't have an IP address.
To me, "the server address" means the IP address used to join a Minecraft server. "My internal IP address" means my computers reserved IP address as stated within my R7960P router. "The server" refers to the one Minecraft server I am trying to make available for others to join.
> Are all the server LAN IP addresses reserved or static?
What do you mean by "all" of the addresses? To try and answer, the only thing that I have done is created one reserved IP address for my own computer, which is the internal IP address shown above within the one port-forwarding rule I have. I don't have any static IP addresses. I have successfully created static IP addresses in the past, but after moving and getting a new router and a new gateway, I haven't been able to successfully create a static IP address on my computer.
> When you run a Minecraft server on one of these computers, are you
> somehow specifying a non-default port number for it (in a "Minecraft
> server file"?), or are they all using the default (25565) on your LAN?
Correct. I am specifying a non-default port number for each Minecraft server that I create within the Minecraft Server Properties folder. As stated above, I don't run multiple at a time and I run these servers on one computer.
> When you connect a Minecraft clinet system to a server, how do you
> specify which (non-default) port number to use?
The client systems are given my computers public IP address along with the assigned port number for the server they are trying to join. That information would be entered within Minecraft in order to join that server.
> It's normally simpler to use Address Reservation[...]
So I don't need to use static addresses then, assuming I have correctly set up my address reservation? (just to be clear)
> Port forwarding rules on the router are a way to tell the router
> where to forward such incoming messages.
Ok. Thank you for that explanation. I think I am starting to understand a bit more about the process. So I've made an address reservation of 192.168.1.200 for my computer, which will be hosting the Minecraft server in question, in order to keep the IP address from changing within my router. Assuming I did the port-forwarding rules correctly, I should be telling all incoming requests to join my specific computer at 192.168.1.200 through the port number that I specified, right?
> Currently I am only trying to run one server on my own computer. I
> have never run multiple at the same time.
> [...] I am specifying a non-default port number for each Minecraft
> server that I create within the Minecraft Server Properties folder. As
> stated above, I don't run multiple at a time and I run these servers on
> one computer.
Ok. So, then, why would you use a non-default port number for this
one server?
> Its rules are as follows:
That's one rule, but ok. Is there a server running on the system at
"192.168.1.200", listening at port ("query.port", I gather) "25585"?
> To me, "the server address" means the IP address used to join a
> Minecraft server. [...]
Sadly, that's ambiguous. From the outside world, you'd need to use
your router's WAN/Internet address (which is your public IP address).
On your LAN, you can use the server's LAN IP address. Or (if NAT
loopback is working), you could also use your router's WAN/Internet
address from within your LAN.
> [...] "My internal IP address" means my computers reserved IP address
> as stated within my R7960P router. [...]
If you mean your computer's (LAN) IP address, then say that. "My" is
not a useful description of an IP address, unless _you_ have an IP
address.
> [...] created one reserved IP address for my own computer, [...]
And what is that address reservation?
> [...] which is the internal IP address shown above within the one
> port-forwarding rule I have. [...]
Wouldn't it have been easier, as well as clearer, to say something
like "192.168.1.200, as in the port-forwarding rule shown above"?
And is that computer really at that address?
> So I don't need to use static addresses then, assuming I have
> correctly set up my address reservation? (just to be clear)
Right. So long as the server system has the IP address specified in
the port-forwarding rule, it doesn't matter how you managed that.
> [...] Assuming I did the port-forwarding rules correctly, I should be
> telling all incoming requests to join my specific computer at
> 192.168.1.200 through the port number that I specified, right?
"I"? The rule in the router should.
If your server is running on the system at "192.168.1.200", listening
at port "25585" (whyever), then you should be able to connect to it
("join") from a system on your LAN by specifying that address and port
(often written as "192.168.1.200:25585").
If your port-forwarding rule is correct (and NAT loopback is
working), then you should also be able to connect to it from a system
on your LAN by specifying the router's WAN/Internet IP address (your
public IP address) and (with your external=internal p-f rule) that same
port number. And anyone in the outside world should also be able to
connect to it by specifying that same public-address+port combination.
What could go wrong?
> So, then, why would you use a non-default port number for this
> one server?It has become a habit I suppose. I have created a handful of servers for Minecraft in the past and the first one used the default port number, so I have always used different port numbers for new servers.
> Is there a server running on the system at
> "192.168.1.200", listening at port ("query.port", I gather) "25585"?Yes.
> And what is that address reservation?
IP Address MAC Address Device Name 192.168.1.200 30:9C:23:CF:ED:57 DESKTOP-9345RMG
> And is that computer really at that address (192.168.1.200)?
Under "Attached Devices" within the R7960P, the computer in question displays the IP address 192.168.1.200. If that isn't what you mean, I will need more explanation.
> And anyone in the outside world should also be able to
> connect to it by specifying that same public-address+port combination.I just had a friend test out joining the server, and it works now! Thank you for your help and patience with me. I really appreciate it.
> [...] I have created a handful of servers for Minecraft in the past
> and the first one used the default port number, so I have always used
> different port numbers for new servers.So, no actual reason?
One reason to use a non-default _external_ port number would be that
some bad actors in the outside world might try to attack the default
port, but not all ports, so using a non-default external port can evade
some simple attacks.Note, however, that a port-forwarding rule can have different
external and internal port numbers, so you could configure your server
to use the default port number (internally, on your LAN), while clients
in the outside world would need to use the (different) external port
number.> [...] it works now! [...]
Glad to hear it.
> What could go wrong?
> So, no actual reason?
Yes, I suppose not.
> Note, however, that a port-forwarding rule can have different
> external and internal port numbers[...]Ok. That's good to know. Maybe I can experiment with that in the future.
Thanks again for all the info and help.
Cheers!