topic Re: Port forwarding to Minecraft server fails, but DMZ works in Broadband & Landline

Port forwarding to Minecraft server fails, but DMZ works

AaronThorne — Sun, 19 Jul 2026 15:36:31 GMT

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

Re: Port forwarding to Minecraft server fails, but DMZ works

JimM11 — Sun, 19 Jul 2026 15:55:55 GMT

@AaronThorne ""The NAS has a reserved local IP address"" reserved were in the DHCP off the EE Hub and set as a static option always use this IP?

Re: Port forwarding to Minecraft server fails, but DMZ works

AaronThorne — Tue, 21 Jul 2026 21:53:16 GMT

Yes it’s a static IP Address,

Re: Port forwarding to Minecraft server fails, but DMZ works

JimM11 — Tue, 21 Jul 2026 22:01:30 GMT

@AaronThorne Try.

Create a new port forwarding rule: Name: Enter a descriptive name like "Minecraft Server." Port: Enter 25565 for both internal and external ports (for Java Edition). For Bedrock Edition, use 19132 and 19133. Protocol: Select TCP/UDP or Both. IP Address: Enter your computer's IPv4 address.
Post a copy off your port forwarding rules up on the Forum.

Re: Port forwarding to Minecraft server fails, but DMZ works

AaronThorne — Sun, 26 Jul 2026 16:03:32 GMT

Here is a screenshot of my rules.

EE had sent out a new router, but still have exactly the same issue 😩
NAS in DMZ all connections are fine. Out of the DMZ no joy at all.
I can connect to the Minecraft Server internally fine.

Re: Port forwarding to Minecraft server fails, but DMZ works

XRaySpeX — Sun, 26 Jul 2026 16:06:52 GMT

Switch uPnP OFF in the Firewall.

Re: Port forwarding to Minecraft server fails, but DMZ works

JimM11 — Sun, 26 Jul 2026 20:38:24 GMT

@AaronThorne The two rules you have get those MAC addresses of only IP will work efficiently.

Re: Port forwarding to Minecraft server fails, but DMZ works

AaronThorne — Sun, 26 Jul 2026 22:08:33 GMT

UPnP is off, the other rules that were created when it was on. I can’t seem to delete them.

any other suggestions?

Re: Port forwarding to Minecraft server fails, but DMZ works

AaronThorne — Sun, 26 Jul 2026 22:09:56 GMT

There are ipv4 addresses assigned to each device. My NAS IS 192.168.1.97. STATIC address.

Re: Port forwarding to Minecraft server fails, but DMZ works

XRaySpeX — Sun, 26 Jul 2026 23:22:23 GMT

Try rebooting router to get rid of them.
They are certainly not IPv4 addys. Look like MAC addys.

Re: Port forwarding to Minecraft server fails, but DMZ works

JimM11 — Mon, 27 Jul 2026 06:18:11 GMT

@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