@Clive_A thanks for that, I have been through that and trawled through the forums already which should be evident from the checks using telnet and CurrPorts etc. If there's anything in particular you think I'm missing that would help you provide a constructive response, then please advise.

  @Hayden-N 

Hayden-N wrote

  @Clive_A thanks for that, I have been through that and trawled through the forums already which should be evident from the checks using telnet and CurrPorts etc. If there's anything in particular you think I'm missing that would help you provide a constructive response, then please advise.

What's the result for each step in that guide? 

I at least need to know them before I find a problem and make a suggestion. 

This still does not make sense to me for a constructive suggestion. Any step in that guide, if there is a problem with that, it would not work. 

  @Clive_A 

1. Yes, the server is accessible from the local network, as confirmed by telnet 192.168.0.100 on each of the ports.

2. Yes, I have verified the port forwarding settings in the router, as confirmed by my screenshot above.

3. Yes, the router is getting a public (static) IP address. I won't share that here for obvious reasons.

4. Yes, I have confirmed with my ISP that they do not block or restrict any ports.

5. Yes, I have restarted the router, the switch, the server - everything. No change.

6. Yes, I have verified that the local firewall on the physical server is passing the ports, as confirmed by my screenshot above.

As for the tips: both online port checkers and telnet have been used to verify, as per above and my previous posts.

If it is of any use, Omada seems to be running / accessible off one of the 10GbE SFP ports (192.168.0.3), whereas I am directing these ports to the 1GbE RJ45 port (192.168.0.100) - though this is likely because Windows 11 is prioritising the 10GbE connection by default and I've not yet started to control the traffic / apply QoS across each of these connections, other than specifically pointing RustDesk to x.0.100. In any case, all three connections to the physical server (x.0.2, x.0.3, and x.0.100) are confirmed working.

  @Hayden-N 

Hayden-N wrote

  @Clive_A 

 

1. Yes, the server is accessible from the local network, as confirmed by telnet 192.168.0.100 on each of the ports.

 

2. Yes, I have verified the port forwarding settings in the router, as confirmed by my screenshot above.

 

3. Yes, the router is getting a public (static) IP address. I won't share that here for obvious reasons.

 

4. Yes, I have confirmed with my ISP that they do not block or restrict any ports.

 

5. Yes, I have restarted the router, the switch, the server - everything. No change.

 

6. Yes, I have verified that the local firewall on the physical server is passing the ports, as confirmed by my screenshot above.

 

As for the tips: both online port checkers and telnet have been used to verify, as per above and my previous posts.

 

If it is of any use, Omada seems to be running / accessible off one of the 10GbE SFP ports (192.168.0.3), whereas I am directing these ports to the 1GbE RJ45 port (192.168.0.100) - though this is likely because Windows 11 is prioritising the 10GbE connection by default and I've not yet started to control the traffic / apply QoS across each of these connections, other than specifically pointing RustDesk to x.0.100. In any case, all three connections to the physical server (x.0.2, x.0.3, and x.0.100) are confirmed working.

That is to say that your WAN info on the controller interface shows the same IP as you try the whatismyip website? 

Strange enough, in my network, port forwarding always works. Even though I have a dynamic IP with DDNS, it always works.

Port forward a simple web interface, will that work? If that works, that means the integrity of the port forwarding(NAT) is fine. That would be a problem with the software.