Reply

Port Forwarding: Connection Timed Out on a WNDR3400v2

BWork
Aspirant

Port Forwarding: Connection Timed Out on a WNDR3400v2

I am attempting to port forward for an ark server to play with people off my network, but whenever I check if my port is open (canyouseeme.org), I get a time out error.

 

What I have done:

  1. Verified that I have a public IP
  2. Verified that my computer has a static internal IP
  3. Launched the server on port 27015 (and 7777) and verified that it is detectable via LAN
  4. Verified that my windows firewall allows those ports and ark through on my computer
  5. Verified that my router is forwarding port 27015 and 7777 to the correct internal IP (UDP+TCP)
  6. Set NAT filtering to open in WAN settings
  7. turned on respond to ping in WAN settings

Is there another step that I am missing?

 

Thanks,

Ben

Model: WNDR3400v2|N600 Wireless Dual Band Router
Message 1 of 4
antinode
Guru

Re: Port Forwarding: Connection Timed Out on a WNDR3400v2

> Model: WNDR3400v2|N600 Wireless Dual Band Router

 

   Firmware version?  Connected to what?

 

> 1. Verified that I have a public IP [address]

 

   _You_, personally, "have a public IP [address]", or the WAN/Internet
interface of your WNDR3400v2 has "a public IP [address]", or what,
exactly?

 

> 2. Verified that my computer has a static internal IP [address]

 

   You "Verified" what, exactly, how, exactly?

 

   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 one should fix the address of a
device, but some implications are different.

 

   All your "Verified's" say that you're happy about things, but provide
no information for anyone else to verify.  And, when your description is
sloppy, there's no helpful context.  As usual, showing actual actions
(commands) with their actual results (error messages, LED indicators,
...) can be more helpful than vague descriptions or interpretations.

 

> 3. Launched the server on port 27015 (and 7777) and verified that it
> is detectable via LAN

 

   "detectable" how, exactly?  What does "via LAN" mean to you?  Using
the server's (LAN) IP address, from some other system on your LAN?

 

> 4. Verified that my windows firewall allows those ports and ark
> through on my computer

 

   "Verified" how, exactly?

 

> 5. Verified that my router is forwarding port 27015 and 7777 to the
> correct internal IP (UDP+TCP)


   "Verified" how, exactly?  Did you look at the (invisible)
port-forwarding rules, or did you actually test some kind of
communication, or what?

 

> 6. Set NAT filtering to open in WAN settings

 

> 7. turned on respond to ping in WAN settings

 

   I wouldn't expect those to matter.

 

> Is there another step that I am missing?

 

   Who could tell?

 

   For the usual problems with port forwarding, see:


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


> [...] whenever I check if my port is open (canyouseeme.org), I get a
> time out error.

 

   What do you get from similar test for a non-forwarded port?  Knowing
nothing about the actual test, I'd normally expect "connection refused"
from a port which is not getting any special handling.  A time-out is
more suggestive of a server or firewall problem.

Message 2 of 4
BWork
Aspirant

Re: Port Forwarding: Connection Timed Out on a WNDR3400v2

1. The router address. I had to contact my ISP as they had been NAT filtering the router.

2. Thank you for the correction, I did in fact mean that I had reserved the dynamic address

As for the verifications, I believe I posted a response to my initial inquiry with screenshots. I know it takes a bit for images to be processed.

3. I was able to connect to the server over LAN

4. I manually went through my firewall and added allowances (they were called rules) for those ports

5. In the router advanced settings, I made a new port forward for those ports and had them sending to the device that had its dynamic address reserved

6,7. Just trying to cover my bases. The help tip on the WAN page said that it could effect hosting game servers

I received the same error “connection timed out” on the other ports. I also attempted other sites with no positive result.

And despite the connection timing out, I was able to get a friend to join the server over the Internet. So despite the issue being resolved, I still want to learn why I wasn’t able to get a response from the port checkers.

Thanks!
Ben

Message 3 of 4
antinode
Guru

Re: Port Forwarding: Connection Timed Out on a WNDR3400v2

> 1. The router address. I had to contact my ISP as they had been NAT
> filtering the router.

 

   Thanks for including all the details.

 

   That's item "1" in the list of usual problems for a reason.

 

> As for the verifications, I believe I posted a response to my initial
> inquiry with screenshots. I know it takes a bit for images to be
> processed.

 

   Pictures take time to be approved, but I see no post with any
pictures, approved or not.

 

> And despite the connection timing out, [...]

 

   With my weak psychic powers, I still can't see any of the actual
things which you did.  If your ISP was using carrier-grade NAT for your
connection, then none of this stuff could work.

Message 4 of 4
Top Contributors
Discussion stats
  • 3 replies
  • 286 views
  • 0 kudos
  • 2 in conversation
Announcements