Port forwarding not working

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
12

Port forwarding not working

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
18 Reply
Re:Port forwarding not working
2024-01-17 20:21:10 - last edited 2024-01-19 12:10:52

  @RogueMan 

 

We've been through pretty much every possible reason for port-forwarding not working - here.

What you can do is to bring up a simple web server on port 80 and test if that will work for you.

If this was helpful click once on the arrow pointing upward. If this solves your issue, click once the star to mark it as a "Recommended Solution".
  0  
  0  
#12
Options
Re:Port forwarding not working
2024-02-01 16:15:52

I've got the same problem. Just I'd like to port forward the SMB (445 port). Doesn't work.

There is useful page Open Port Check Tool - Test Port Forwarding on Your Router, (OPCT), where you can check the opened port from internet. It showed that 445 is closed.

I've tried to translate the port as well, from 4445 to 445. OPCT showed 4445 is closed. I've tried these with NFS ports (1058, 2049) as well. Doesn't work.

However, if I tried with RDP (3389), OTCP showed 3389 as opened. Moreover, I did a 4445 => 3389 translation, OPTC showed the port 4445 opened.

So, basically the forward method works.But I guess, that it doesn't work for all port, but just for the ports listed at predefined Application ports. (3389 is there, but 445 or 2049 aren't)

  0  
  0  
#13
Options
Re:Port forwarding not working
2024-02-01 16:38:22

  @Hiritomi 

 

Port-forwarding can work with non-predefined ports as well (like 4445 in your tests).

Some ports like 445 can be closed/blocked at the ISP level though.

If this was helpful click once on the arrow pointing upward. If this solves your issue, click once the star to mark it as a "Recommended Solution".
  0  
  0  
#14
Options
Re:Port forwarding not working
2024-02-01 18:48:26
Sure. But the ISP does not block: a Huawei HG8143A5 router (before my current TP-Link router) did forward the 445. Now: 4445 => 445 (SMB): OTCP shows closed 4445 => 1058, 2049 (NFS): OTCP shows closed 4445 => 3389 (RDP): OTCP shows opened So, ISP does not block 4445. If the router forwarded the port 4445 to 445, then OTCP should show port 445 opened
  0  
  0  
#15
Options
Re:Port forwarding not working
2024-02-01 19:04:49
If port forward 4445 => 445 worked on the router, OTCP should show port 4445 opened, independently from the ISP
  0  
  0  
#16
Options
Re:Port forwarding not working
2024-02-01 19:38:09

  @Hiritomi 

 

Yes, that's correct, but I've mentioned this in general. I doubt that you would be able to open ports like 135, 137 or 445 on a home router for security reasons.

If this was helpful click once on the arrow pointing upward. If this solves your issue, click once the star to mark it as a "Recommended Solution".
  0  
  0  
#17
Options
Re:Port forwarding not working
2024-02-04 16:38:35
Thx. So, if I'm right, we agree that TP-Link router blocks 445 port forward in all forwarding rules (445=>445 and 4445=>445 as well), not the ISP. Why does it block??? By default, nothing is forwarded. It is OK.But, if the user wants to forward port 445, then it is the user's responsibility. Why TP-Link blocks user action? Why is it not in the manual? Why doesn't refuse such a forward rule on the configuration page, letting configuring users is doubts???
  0  
  0  
#18
Options
Re:Port forwarding not working
2024-02-04 17:23:19

  @Hiritomi 

 

I can only assume but you can go through this thread to see why this does pose a security concern - <https>://forum.mikrotik.com/viewtopic.php?t=187292

If this was helpful click once on the arrow pointing upward. If this solves your issue, click once the star to mark it as a "Recommended Solution".
  0  
  0  
#19
Options