NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
r7000 port forwarding failed
Hello, I recently attempted to setup port forwarding on my new r7000 router and am having some trouble. I tried perusing the forums for other threads with the same issue and tried a few fixes to ...
Thanks for the reply!
Actions I believe I described below after you asked but let me know if you need more info... No error message other than a port checker shows "closed" and I can see the game hosted and can join internally from my network but my friend cannot externally.
I set a static IP on my pc, no reservation is set in the router.
Yes same ports for external/internal. See attached screenshot. After posting this thread, I tried setting these up as separate rules for each port instead of the range, but that did not help (a separate service rule for each port, 3 in total 2456 2457 and 2458. Let me know if you want to see that screenshot, can only attach 1 it seems.)
Application is a game called Valheim - from what I found on various thread it uses the 3 above ports. (links to threads I checked: https://www.pcgamer.com/valheim-multiplayer-dedicated-server/ and https://www.shacknews.com/article/122720/how-to-set-up-a-valheim-dedicated-server).
> [...] I can see the game hosted and can join internally from my
> network but my friend cannot externally.
Using which IP address? See item "3". Test both.
> I set a static IP on my pc, no reservation is set in the router.
The danger with that is that the DHCP server in the router could
still grant that address to some DHCP client device. (Especially for a
low value like ".3".) If you're using real static addresses, then
shrink the DHCP pool, and use only ex-pool addresses as static
addresses. (For example, change ".2" - ".254" to, say, ".5" - ".254".)
> [...] See attached screenshot. [...]
Looks ok to me.
Good morning, thanks for the reply!
I updated my DHCP pool as recommended and shrunk it to .2 - .200 and updated my PC's static IP to .201. I then updated the port forwarding rules to point to the new internal IP address of my machine.
So you bring up a good question, when I went to connect I was able to just join via the community server browser in game as the server was showing up there properly.
I tried to connect via IP at 192.168.1.201:2457 and was successful. I also tried my external IP 73.243.xxx.x.:2457 and that also was successful. However a port checker still shows 2457 is closed when I am connected to the server. My friend is not on to test right now to join but I suspect he won't be able to see it if a port checker still shows it closed.
What is interesting is that when I browse servers via the Steam server browser (note this is separate from the Valheim in game server browser) that is outlined in one of those guides I can see my game with my public IP, but it shows port 2456 being used and states server is not responding. However I confirmed my server batch file is pointing to use 2457 and confirmed I can still join via the browser in game by internal/external IP at 2457.
> I tried to connect via IP at 192.168.1.201:2457 and was successful. I
> also tried my external IP 73.243.xxx.x.:2457 and that also was
> successful. [...]That would seem to exonerate the router. There's also item "4". Or
application-specific problems.