TeamSpeak server not working - No UDP support on EE networks?

[Booce2024]

Hi All, I have a Teamspeak server running on its default port of 9987 but it requires UDP. This has worked for years on Virgin and BT but now I have switched to EE, no-one can connect to it. I have my own router which I can connect directly to ONT which I have done as the DMZ and port forwarding on the EE superhub + didn't make a difference and it doesn't work on that either. Are EE blocking all UDP traffic? I'm a network engineer so trust me when I say the ports are all forwarded correctly. It works internally but no joy whatsoever externally. Is there any hope? Should I be shouting at EE directly?

Thanks for any responses.

[XRaySpeX]

EE doesn't block UDP ports.

Please post your Port Forwarding settings.

What does ShieldsUP! report the status of your ports when you use its All Service Ports & also your opened ports with User-Specified Custom Port Probe ? Are they shown as "Closed" or "Stealth"?

[bobpullen]

Definitely not blocking UDP in my experience. I'm hosting a VPN server on UDP port 1194 and I can reach that without issue from the Internet (with the requisite port forwarding in place).

---

@Booce2024 wrote:

I have my own router which I can connect directly to ONT which I have done as the DMZ and port forwarding on the EE superhub + didn't make a difference and it doesn't work on that either.

---

I'm a bit confused by this. Can you elaborate on exactly how you have things set up? Is this the same setup you were using with BT, or did you come rom Virgin? Why do you have two routers on your network?

[Booce2024]

Sorry for the delay responding, Outlook decided the reply notifications junk. EE router has my internal router set as being in the DMZ so no rules there. The Asus router forward external traffic as below

TS2

9987

9987

192.168.0.2

UDP

I can't see how to get shields up to probe UDP rather than TCP so I added both protocols to the rule and shields up reports

9987

Closed

Unknown Protocol for this port Unknown Application for this port

However I have some 20 odd rules for various other services which are all working fine albeit all are TCP. Other port rules are being reported as open and stealthed.

[Booce2024]

I have tried two different set ups, one with the EE router connected to the ONT with my router attached to the EE router. My router has the UDP rules to forward to 9987. The EE router has my router in its DMZ so no rules should be required there. I have also tried it with no EE router and the ONT connected directly to my router with the forwarding rules. Neither allow connections from outside my network.

[XRaySpeX]

@bobpullen : What does ShieldsUP! report the status of your port 1194?

[Booce2024]

1194 reports as failed which I would expect as I do not have that port open. This setup worked when I was on BT ADSL and Virgin cable with the virgin router in modem mode and the BT router having my router in the DMZ.

[bobpullen]

---

@XRaySpeX wrote:

@bobpullen : What does ShieldsUP! report the status of your port 1194?

---

It won't show anything of worth because the ShieldsUP! probes use TCP and my VPN server is listening on UDP.

[XRaySpeX]

Ah, OK! That's what I was trying to get you to confirm.