Port Forwarding not working no matter what I do

A

Alien

Member
Right, so I've been tearing my hair out over this the past few days. I've consulted multiple sources but I cannot find fault with what I am doing.

UPnP is enabled, the router's firewall is set to low, both my computer and antivirus' firewall are disabled and I'm fairly confident that I have set up the port forwarding correctly. I have also made it so WAN to LAN packets are permitted and assigned my computer a static IP address. No matter what I do, a port checking tool tells me that the port is closed and this is confirmed by the fact that I cannot establish a connection to the application which requires the port 52757.

These are my port forwarding settings. I've tried multiple combinations for the settings, such as separating the TCP and UDP protocols into different rules, putting them both together and trying them individually, all to no avail.
fa4747f90db9e81b1e7aab79c1c4c0d3.png


Can anyone offer some insight as to why I am having this trouble? Thanks in advance guys.
 
Last edited:
Port forwarding only involves the specific IP of the computer you want to have access. Do not enter IP of the router use the IP of the computer.
 
johnb35 said:
Port forwarding only involves the specific IP of the computer you want to have access. Do not enter IP of the router use the IP of the computer.
Click to expand...

Apologies, this was a copy and paste from another forum. Forgot to make amendments to the original post. I have since only included my computer's IP and removed my router's IP.
 
Probably a ridiculous one but can you verify that the application is actually listening on 52757?

Usually there isn't too much to it, just verify that you have the forwarding rule on your WAN/NAT edge, have the appropriate firewall rule on your endpoint firewall and have the service as listening on that port.

52757 seems like a weird service port unless you manually set the application to listen on that port. High level ports are typically used as dynamic client-side ports.

Do you have multiple routers in your topology or just one?
 
beers said:
Probably a ridiculous one but can you verify that the application is actually listening on 52757?

Usually there isn't too much to it, just verify that you have the forwarding rule on your WAN/NAT edge, have the appropriate firewall rule on your endpoint firewall and have the service as listening on that port.

52757 seems like a weird service port unless you manually set the application to listen on that port. High level ports are typically used as dynamic client-side ports.

Do you have multiple routers in your topology or just one?
Click to expand...

I believe it was at the time, but just in case I was incorrect I also had a port triggering application ensuring that something is definitely listening on the port.

I've tried both adding the ports as rules to my firewall and completely disabling the firewall, no matter what happens I just can't seem to get it to work.

As for the port, I got it from an application that picks any port between 10000 and 65535. It picked 52757 so I went with that one. I had also tried a different port, but to no avail.

I only have one router on my network.
 
Can you connect to your server using the client application from your local PC or within your LAN?

What program is it, anyway?
 
beers said:
Can you connect to your server using the client application from your local PC or within your LAN?

What program is it, anyway?
Click to expand...

I'm not sure what you mean by this first sentence? Apologies.

Vuze. It's a BitTorrent client (Only for legal things, I assure you! My ISP is extremely strict).
 
You should be able to use something like PuTTY and telnet within your LAN to that IP and port. If it times out then you can't connect locally and it's a local issue, but if you get an open connection then it's a problem on the WAN/port forward side instead.

Since there are a few steps that could go awry just trying to narrow it down more specifically.
 
beers said:
You should be able to use something like PuTTY and telnet within your LAN to that IP and port. If it times out then you can't connect locally and it's a local issue, but if you get an open connection then it's a problem on the WAN/port forward side instead.

Since there are a few steps that could go awry just trying to narrow it down more specifically.
Click to expand...

I hope I've done this correctly. I've enabled Telnet within Windows and I used the command "open 192.168.1.3 52757", which is my computer's IP and the port which I wanted to open. I've also tried my router's IP and the default port Telnet attempts to connect to. All of these result in the error message "Could not open connection to the host, on port 52757: Connect failed".
0705c1deb450ba3bac008c91f2404df9.png
 
As beers mentioned it really sounds like you are forwarding the port that its communicating on but not the one that listens for incoming connections. Particularly this part
As for the port, I got it from an application that picks any port between 10000 and 65535.
Click to expand...
Vuze says the following ports by default:
Which ports does Vuze use by default?[edit]

When you first install Vuze, it selects the "main port" for torrent downloading/uploding usage by random. As described previously, you can change that to something else if you like.

Vuze also uses some ports for internal use and/or as defaults for some functionality:
1900 UDP: Used for UPnP?
6880 TCP: Vuze uses this port for internal communication. When you launch Vuze, it always checks that port for an older instance of Vuze being already active. If there is an active Vuze, then the new Vuze instance passes the possible torrent name as parameter to the old instance already running and then dies. (This happens e.g. when you click a "download torrent" link on a web page. A new second Vuze instance gets launched by the browser, but it dies after passing the argument to the old Vuze.) If there was no active old Vuze, then the new Vuze reserves that TCP port and starts "listening" there.
6969 TCP: If you enable internal HTTP tracker, this is the default port used. You need to port-forward this port in router for full connectivity.
7000 TCP: Default port for HTTPS tracker. (usually not in use)
16680 UDP: Used for the 'LAN peer finder' functionality.
45100 TCP: Used for magnet URI handling.
49001 UDP: Used for Mainline DHT (if that plugin is installed). You need to port-forward this port in router for full connectivity.
Click to expand...
 
Cromewell said:
As beers mentioned it really sounds like you are forwarding the port that its communicating on but not the one that listens for incoming connections. Particularly this part

Vuze says the following ports by default:
Click to expand...

To be honest, I really have no idea what I'm doing, but I'm almost certain I have everything set up correctly.
This is what Vuze says:
5686ef0f02255cc8604ed39eb9f629ba.png


Can either of you suggest an application and a port to forward just so I can try and see if port forwarding works at all?
 
I was conferring with someone else about my problem and we discovered that my internet is refusing certain requests. He attempted to ping my IP and the connection was rejected. Does anyone know a reason that this could happen?
 
Some routers by default don't respond to ICMP inquiries that originate from the Internet.

Since you can't connect locally on your LAN to that service port, I'd sort that side out first before blaming your ISP.
 
beers said:
Some routers by default don't respond to ICMP inquiries that originate from the Internet.

Since you can't connect locally on your LAN to that service port, I'd sort that side out first before blaming your ISP.
Click to expand...
When you said that it reminded me of something that I had seen before in my router which said ICMP...

I changed this from LAN to WAN & LAN, would this make any difference? There are also several other tabs as seen in this picture, most are set to LAN only with FTP and SNMP being set to disabled. Should I change any of these?
039cbf458a8e93a4e8ee77148ab2fd63.png
 
beers said:
Some routers by default don't respond to ICMP inquiries that originate from the Internet.

Since you can't connect locally on your LAN to that service port, I'd sort that side out first before blaming your ISP.
Click to expand...

Also with Comcast router TG862 you wont be able to Port Forward without the Authorization of Comcast.
 
Enabling ICMP won't fix your problem. That will do things like let your router answer ping externally.

It's been said already, but until you can connect to the server locally with a client there's no point trying to figure out your port forwards. They may be working. They may not. You can't tell.

If you are insistent on testing forwards first, a simple way to verify port forwarding works is to grab a simple webserver (or ftp server -- port 21) and configure it to listen on 8080 then forward that port to your IP and see if you can connect via your external ip address.
 
Cromewell said:
Enabling ICMP won't fix your problem. That will do things like let your router answer ping externally.

It's been said already, but until you can connect to the server locally with a client there's no point trying to figure out your port forwards. They may be working. They may not. You can't tell.

If you are insistent on testing forwards first, a simple way to verify port forwarding works is to grab a simple webserver (or ftp server -- port 21) and configure it to listen on 8080 then forward that port to your IP and see if you can connect via your external ip address.
Click to expand...

I was asking someone else about this problem, and I was told to enable the World Wide Web services program and try and connect to it with another device on my network. The website loaded on my phone, which I believe indicates that there is no longer a problem locally?

Agent Smith said:
Grc has shields up that can test the port and then there is PFPortChecker.

http://portforward.com/help/portcheck.htm

https://www.grc.com/x/ne.dll?bh0bkyd2

Check portforward.com and see if your router is listed. It will have a guide on how to properly port forward in your device.
Click to expand...

I've checked portforward before, and while they have a method for my router, the screenshots are not actually from my router's webpage and so are not useful for me. Their tool also says all of the ports that I enter are closed.

I used the grc tool and it showed all of my ports as stealth... Which I understand means that they drop connections that they receive? Does this mean port forwarding will not work unless I make it so they are not stealth?
 
Alien said:
I was asking someone else about this problem, and I was told to enable the World Wide Web services program and try and connect to it with another device on my network. The website loaded on my phone, which I believe indicates that there is no longer a problem locally?
Click to expand...

That's a different service that has nothing to do with the application you're trying to allow.. It sounds like they had you launch a web server (IIS). You can connect since the application is listening on it.

If you really just wanted to test port forwarding anyway you could forward something like external 50000 to internal 80 for that host and then try to have an external/Internet source browse to http://external-ip-here:50000

I used the grc tool and it showed all of my ports as stealth... Which I understand means that they drop connections that they receive? Does this mean port forwarding will not work unless I make it so they are not stealth?
Click to expand...

For a forwarded port it should usually show open if the service is forwarded and listening. If you are filtering by source IP it may show closed or stealth (which you most probably aren't). Usually you will see closed if the service is not listening on that port but the port is forwarded.


What are you even trying to accomplish anyway? Most torrent clients utilize UPnP to begin with. Are your uploads just sucky?
 
Alien said:
Right, so I've been tearing my hair out over this the past few days. I've consulted multiple sources but I cannot find fault with what I am doing.

UPnP is enabled, the router's firewall is set to low, both my computer and antivirus' firewall are disabled and I'm fairly confident that I have set up the port forwarding correctly. I have also made it so WAN to LAN packets are permitted and assigned my computer a static IP address. No matter what I do, a port checking tool tells me that the port is closed and this is confirmed by the fact that I cannot establish a connection to the application which requires the port 52757.

These are my port forwarding settings. I've tried multiple combinations for the settings, such as separating the TCP and UDP protocols into different rules, putting them both together and trying them individually, all to no avail.
fa4747f90db9e81b1e7aab79c1c4c0d3.png


Can anyone offer some insight as to why I am having this trouble? Thanks in advance guys.
Click to expand...

There's a sticky thread in this sections for my guide: http://www.computerforum.com/232855-how-port-forward.html
It may or may not be helpful if you haven't taken a look already.

FROM THIS IMAGE YOU HAVE, try to set the port number above and below what you're trying to open. Some routers have issues and won't open the port if the start and end ports are the same.

ISP's can also block forwarding if you're using a router model they own.
 
You must log in or register to reply here.
Back
Top