NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Unsuccessful with opening port using service
I seem to be having a problem with getting a port open on my router. I have added a service linked the port needed to my PC's internal IP address. I've done this before and it worked. I'm trying to setup a connection with a remote server, and to aid in opening the connection I have also added rules in my Windows Firewall, both inbound and outbound. Somehow when configuring the port forwarding rule (service as Netgear calls it), when checking the port online through https://portchecker.co/ or https://canyouseeme.org/ each tell me the port is still closed. I'd like some guidance on what I need to do because I am clearly not doing this right.
Currently, I have configured an FTP service using TCP port 49152. As mentioned, this is routed to my PC.
This is the result when testing the port on both websites.
What makes no sense to me is this, traffic from an external source may not necessarily be coming from this port, but this is the port it is targeting on my system. Why would it make any sense to pin down one port for both the external system and my system, especially if traffic is not guaranteed to come from port 49152?
2 Replies
- Online port checkers need a service listening on the mentioned port to report it as open. If nothing is listening on that port, they report it as closed.
Port forwarding is in general easy and reliable. Permitting the router WAN/Internet interface does have a public IP route-able address, the ISP does not have any restrictions like software firewalling.
Does the router Internet/WAN port show as using the same public IP address like your DDNS provider does point to?
Could there be probably -two- or more NAT routers in the data path, like an ISP modem-router plus the Netgear router?
More difficult, as you talk of an FTP service, for most non-IT network admins, this can proof to be a can of worms to the new network admin. Not all ftp clients can be configured easily to behave like the user expect - and more the FTP protocol suite - does require. Real FTP does consist of two concurrent connections (and ports), one for ftp-control, and one for ftp-data
If desperately have to use FTP, start with an ftp client offering good insight of what is going on on the connection attempt, like FileZilla
And seriously, most problems are not related just to port forwarding (port open on the router), but are related to the idea of let's use ftp - as it does sound simple. Alone real FTP does not just work on a single port like 49152/TCP - but it's certainly a starting point, and you don't have to use the default ftp-control port.
To cause more confusion, FTP can be implemented also using SFTP (SSH protocol based - unless Microsoft extended the capabilities recently, Windows does not provide support for this), and FTPS (better FTPES).
What service, what server (hey, I've seen you talk of your PC, likely Windows) you intend to operate, and what clients, and what user base you intend to be workable for this "FTP" connection?
