Deco M4 Port Forwarding Weirdness

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

Deco M4 Port Forwarding Weirdness

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Deco M4 Port Forwarding Weirdness
Deco M4 Port Forwarding Weirdness
2020-01-31 19:14:14
Model: Deco M4  
Hardware Version:
Firmware Version: 1.9.18

Hey, First time here. Have searched and not found the same issue in the forum. 

 

I'm having strange behaviours with Port Forwarding. 

 

First off, I've ruled out the NAT issue. The IP of the TP Link is indeed public. 

 

So here's what I've done and the issue I'm seeing. 

 

I've setup 4 Port forwards: 

 

1. Remote desktop (3389) - Works great. 

2. A download service (8765) - Works great. 

3. A web service based on the same server as #2 - DOESN'T WORK. 

4. Another version of #3 - DOESN'T WORK. 

 

That's it, 2 port forwards work great, two don't. 

 

I've troubleshooted in the following ways. 

 

Confirmed that the ports are indeed working via localhost:port number however, they don't work on an internal lan when using the IP address of the server directly.  

Tried 3 - 4 different ports for each of these services and they still don't work. 

Tried ports for "Standard services" like FTP - then ran port checks to see if they're open and they aren't. 

 

I had all these ports forwarded before upgrading to the TP Link Deco system, and they worked fine and nothing has been changed in the config of the web services themselves. So it's definitely the router not liking them for some reason. 

 

Very odd that two ports are all good, and these two are NOT. 

 

It would appear I have some kind of 2 port limit. 

 

Anyone had the same issue? The App is so basic that I can't really troubleshoot any further, so it's very frustrating. 

 

Any help would be greatly appreciated! 

 

 

  0      
  0      
#1
Options
1 Reply
Re:Deco M4 Port Forwarding Weirdness
2020-01-31 19:26:45

Ah jeez. It's the bloody firewall on my server. 

 

Switching networks defaulted it to a Public. 

 

indecision

  0  
  0  
#2
Options

Information

Helpful: 0

Views: 1568

Replies: 1

Related Articles