cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Port forwarding to Minecraft server fails, but DMZ works

AaronThorne
Investigator
Investigator

Hi,

I’m trying to host a Minecraft server from my DXP4800 Pro NAS using Crafty Controller, Paper, Geyser and Floodgate.

The server works correctly on my local network for both:

  • Java Edition on TCP port 25565

  • Bedrock Edition on UDP port 19132

External connections also work when I temporarily place the NAS in the router’s DMZ. However, they stop working when I remove the DMZ and configure individual port-forwarding rules. My current rules are:

  • External TCP 25565 → NAS IP, internal TCP 25565
  • External UDP 19132 → NAS IP, internal UDP 19132

  • UPNP off.

The NAS has a reserved local IP address, and I’m testing externally from an iPhone over mobile data with Wi-Fi disabled. I have also tried alternative external ports mapped to the standard internal ports, but that hasn’t resolved it.

Because the DMZ test works, the Minecraft server, Docker port mappings and external connection itself appear to be functioning. It seems that the router is not applying the individual forwarding rules correctly.

Router model: Smart Hub 6 Plus
EE broadband package/connection type: Full Works: Full Fibre Gigabit
Router firmware version: r4.26.3-R-1923144-PROD-83002

Has anyone successfully configured separate TCP and UDP port forwarding on this router? Are there any additional firewall, IPv6, UPnP or port-sharing settings that need changing?

I have removed the NAS from the DMZ because I don’t want to expose all of its services publicly.

Any advice would be greatly appreciated.

TIA

Aaron

10 REPLIES 10

@AaronThorne You may just have to treat it the same way as the linked post, get all your devices off the network before the reset and then get your rules done before the uPnP ever get's in.

Solved: Smart Hub 7 plus - Port Forwarding horror. - The EE Community