NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Port forwarding issues
Hi, I'm trying to forward some ports on from my router to my PC but am having quite a bit of trouble.
As you can see in the screenshot below. I have added both of the required ports to allow co...
I've gone into the Netgear genie and reserved the IP address for my device - 192.168.0.35
The public IP of my router beings with 58.107
Not sure what you mean by "Server program"
> I've gone into the Netgear genie and reserved the IP address for my
> device - 192.168.0.35
What is your "my device"? And is it now at that address?
> The public IP of my router beings with 58.107
Ok.
> What is the target server ("Internal") IP Address in your
> port-forwarding rules?
Still wondering.
This whole Q&A thing works better if all the questions get answered
the first time they're asked.
> Not sure what you mean by "Server program"
When a message from the outside world arrives at (the WAN/Internet
interface of) your router, a port forwarding rule tells the router to
forward that message to a computer at some particular LAN IP address and
port number. What happens to that message when it arrives at that
computer? Some (server) program must be running on that computer which
is listening at that port number, or else that message will be ignored.
If you tell the post office to forward your mail to a vacant lot,
then it won't get delivered.
> [...] I'm trying to forward some ports on from my router to my PC
> [...]
Why?
- > What is your "my device"? And is it now at that address?
Windows 10 PC, yes
> What is the target server ("Internal") IP Address in your
> port-forwarding rules?
192.168.0.35
The ports are to be used by the application 'Destiny 2'.
Based on the developers recommendations the two ports from the screenshot should be forwarded to the device running the application.Your port-forwarding rules (at last) look ok to me.
> [...] Based on the developers recommendations the two ports from the
> screenshot should be forwarded to the device running the application.
Are you "running the application" when you do your tests? That was
what this question was asking:
> Is the server program running on the target server system?
Can you communicate with this server program at 192.168.0.35 from a
client program running somewhere on your LAN? If that fails, then all
the port forwarding in the world won't make it accessible from the
outside world. If the router is doing "NAT loopback" correctly, then
you should also be able to communicate with this server program at the
router's WAN/Internet (your public) IP address (58.107.x.y) from a
client program running somewhere on your LAN. (That would involve the
router's port forwarding.)
> [...] when I check if the ports are open via the following website
> [...]
How much confidence have you in that "open port checker"? Do you
know if it tests UDP? After a little thought, it's not clear to me that
it's possible to test UDP access if the server program does not respond
to an arbitrary test packet which might be sent to it. The actual
client program might make a much more trustworthy test. (With TCP,
there's more handshaking, and a connection can be detected without any
transfer of user data. I don't think that reception of a UDP packet can
be detected by the sender, unless the recipient replies.)- >Are you "running the application" when you do your tests?
Yea, it is running when using the online port checker.
> Can you communicate with this server program at 192.168.0.35 from a client program running somewhere on your LAN.
The program I'm trying to use is a video game, there is no way i can test the connection within the program itself other than when I'm expericing issues within it.
>How much confidence have you in that "open port checker"?
I'm not sure of any other way to test if the ports are open.