NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
R6020 - Port forwarding, not working
Hi! I have a R6020 router and I'm trying to open a port to one of my devices. The instructions I've been given is log into my router and set up a static IP adress for that specific device (i.e n...
Ok, thanks. But how do I check if the port is open then? (if not using an online port checker). The Device I'm trying to open TCP 44158 towards is in a status called "relayed", meaning that it can communicate with others but not vice versa. As long as the port isn't open the status is still there (which it is). So the port does not seem to be open.
> I have a R6020 router [...]
Firmware version? Connected to what?
> [...] I'm trying to open a port to one of my devices. [...]
In my experience, people who talk about ports being "open" or
"closed" often don't understand the problem.
> [...] The instructions I've been given [...]
Can others see these "instructions", too?
> [...] is log into my router and set up a static IP adress for that
> specific device [...]
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.
That address reservation looks ok. Is your target device actually at
that IP address (192.168.1.2)?
> [...] and then do a port forward.
That port-forwarding rule looks ok (for port 44158 on a device at
192.168.1.2), except that the lame router firmware doesn't display the
protocol(s) you specified (TCP and/or UDP).
> [...] I've also read [...]
Where?
> [...] that I should enable dmz to the IP of the device.
Port forwarding should do the job, without passing every attack on
any port to your Default DMZ Server.
For the usual problems with port forwarding, see:
https://community.netgear.com/t5/x/x/m-p/1859106
> [...] But how do I check if the port is open then? [...]
The point is that port forwarding is useless if nothing which is
running on the target server is listening at the target port.
Locally, you should be able to test the target server for a TCP
connection using a Telnet command. (Usual problem 3.) For example:
telnet 192.168.1.2 44158
telnet <router_WAN/Internet_IP_address> 44158
> [...] a status called "relayed", [...]
I don't know what that really means.