Port forwarded but port still closed?

May 26, 2018
8
0
10
I recently got a Huawei HG8245H modem. A router is connected to the Huawei modem. My computer is directly connected to the Huawei modem, not the router. I've been trying to forward a port, but whenever I use a port checker with my IP from websites like ipchicken.com, it says that the port is closed.

Here's a screenshot of my forwarded port. (Click here)
 
Solution


Well that's interesting! Normally your WAN ip is your public ip. But if they're different, than you can't port forward based on your public IP. Something else lies between your WAN and that public IP, and that would require port forwarding from that public IP to your WAN ip.

This is exactly what happens when the ISP places you on a private IP. But I've never seen it done w/ what normally is a public IP. But perhaps your ISP has decided to place you on a public IP, but it's still internal to his network and not directly accessible...

BuddhaSkoota

Admirable


You must also enter the External Port Number and External Source Port Number (same as Internal Port Number entry).

Leave the External Source IP Address blank.
 
You do NOT want to use the External Source Port Number, anymore than you typically want to use the External Source IP Address. Why External Source Port Number is even offered as an option is baffling. It's highly likely the External Source Port Number is arbitrary. But the use of the External Source IP Address would make sense if you wanted to limit access to the port forward to someone from a specific public IP.

Frankly, I don't know why they didn't put External Source Port Number right underneath External Source IP Address. Would have made more sense. Placing it in the subsequent section is misleading.

Typically what you need is Internal Host, Protocol, Internal Port Number, and External Port Number. Leave anything referencing "Source" blank/zeroes.
 
May 26, 2018
8
0
10

Thank you both so much for your answers. Unfortunately, the issue still remains. (Note: In fact this is what I was initially trying, both internal and external ports, excluding the source ports. I'm not sure why it wasn't there in the photo I shared earlier.) Here's a link to some screenshots of my new configuration along with the result of a port checking tool online. (Click here)

Thank you so much for your time.

Kind Regards,
Danish
 
Btw, please clarify the following statement in your opening post.

I recently got a Huawei HG8245H modem. A router is connected to the Huawei modem. My computer is directly connected to the Huawei modem, not the router.

According to my research, the Huawei HG8245H is a combo modem+router. You then state your computer is connected directly to the modem. But that's not possible w/ a modem+router unless it's placed in bridge mode. Bridge mode demotes the device to being just a modem. All routing functions are disabled and irrelevant, including port forwarding. It's up to either your computer's firewall to allow or not allow traffic in from the modem, or if you've connected some other router to that modem, to port forward on that other router.

The point I'm getting at is, your opening post is a bit confusing. I would have expected to you to just say that you have Huawei HG8245H modem+router, and your computer is connected to one of its LAN ports. Period. And in that case, you would port forward on the Huawei HG8245H modem+router. But you didn't. You went out of your way to say it's connected to the modem, not the router.

So I want to be sure we're all on the same page here. As I said, if the Huawei HG8245H modem+router has indeed been placed in bridge mode (which ppl sometimes do because they want to use their own router w/ that device), then port forwarding on the Huawei HG824H will NOT work, since it's now only a modem. That responsibility would pass to either your own router, or whatever other device was directly connected to the Huawei HG824H.
 
May 26, 2018
8
0
10


Edit 2: Kindly click on this link below which leads to a diagram explaining my situation. (Click here)

Thanks for the reply Eibgrad. I am really sorry for the confusion I may have caused. I wasn't fully aware of the proper terminology. Allow me to clarify what my situation is. An optic cable enters into my house into the Huawei. The Huawei has 4 LAN ports. One of these is connected to my PC through a LAN cable, and another one of the four is connected to a router in my house through a LAN cable, because the Huawei's Wifi capabilities were insufficient for our usage. I had the exact same set-up before, but instead of the Huawei there was a ZTE router/modem, in which port forwarding worked perfectly.

Edit: The Huawei also does send Wifi signals, they just didn't reach all the rooms in the house so we plugged a router into it through a LAN cable and placed that router near those zones with weak signal.

Thank you so much for your time.

Kind Regards,
Danish
 
Ok, so this other router you were originally speaking of is completely irrelevant to the discussion.

Any chance your ISP has you on a *private* IP network rather than a public IP? In order to preserve the limited number of available public IPs in the IPv4 space, some ISPs are known to place their customers on the private IP space (e.g., 192.168.x.x, 10.x.x.x, 172.16.x.x). You can verify this by checking the IP assigned to the WAN on your Huawei HG8245H modem+router. If it's a private IP, then port forwarding won't work! It *must* be a public IP.
 
May 26, 2018
8
0
10


Thanks for such a quick response. Kindly click on this link below which leads to a diagram explaining my situation. (Click here)

Moreover, as for the WAN information, the same link above should also have a photo of my WAN information.

Kind Regards,
Danish
 
May 26, 2018
8
0
10


That's great. But in the photo there are two items under the heading of WAN. The second one starts with 10, so does that have any significance? Really by the way, thank you so much.

 
May 26, 2018
8
0
10
Also I noticed something strange. Is the 100.76.x.x supposed to be my public IP? It does not match the IP which is displayed on websites like ipchicken.com. The one displayed there is 103.217.x.x.
 


That appears to be for your VOIP adapter. And it does appear to be a private IP. However, that's not unusual. The VOIP is probably using a VPN client to connect over the WAN to a VPN server, and the tunnel established by the VPN usually uses private IPs. So nothing unusual there.
 


Well that's interesting! Normally your WAN ip is your public ip. But if they're different, than you can't port forward based on your public IP. Something else lies between your WAN and that public IP, and that would require port forwarding from that public IP to your WAN ip.

This is exactly what happens when the ISP places you on a private IP. But I've never seen it done w/ what normally is a public IP. But perhaps your ISP has decided to place you on a public IP, but it's still internal to his network and not directly accessible from the internet. I would ask the ISP if this is the case. Or at least explain why your WAN ip (which he assigns to your router) is not the same as the public IP you see from ipchicken.
 
Solution
May 26, 2018
8
0
10


Thank you so much for helping me! You were right. Apparently my ISP used to give out static IPs for free to all its customers, but recently decided to charge for it, and naturally turned ours into a dynamic IP. According to them, if I get a static IP for an extra monthly free, I would be able to port forward.

Thank you so much, eibgrad, for your constant time and efforts in helping me.

Kind Regards,
Danish