topic Re: EE blocking ports externally in Broadband & Landline

EE blocking ports externally

Baba_Jyaga — Wed, 04 Sep 2024 17:42:36 GMT

i have issue a week ago i started experiencing during playing PUBG, when before everything was butter smooth, now reloading between battles can taken even 5 minutes when game hangs in the reloading screen, after extensive testing including placing pc in DMZ conclusion is ISP is blocking some ports, after calling support i was told no-one is trained or cannot escalate as it does not exist with company structures, only help offered is engineer but it is not "hardware" issue and i cant understand how such a big service do not have tech service.

yet does any one has an idea how or who would be able to help and check if my service is not restricted by port closing.

port forwarding doesn't help - i know other people had similar issues and after calling thier ISP they confirmed the "theory" and adjusted the service.

Re: EE blocking ports externally

Northerner — Wed, 04 Sep 2024 18:32:11 GMT

Hi @Baba_Jyaga

Are you on fixed line broadband or 4G/5G mobile broadband.

Which router do you have.

If ports are blocked then you wouldn't be able to play whatsoever. I suggest your issue is latency. Have you tried turning your router off for 20 seconds.

Thanks

Re: EE blocking ports externally

Baba_Jyaga — Wed, 04 Sep 2024 18:40:20 GMT

i have fixed 1GB line, i have tested it with 2 different routers, standard ee hub and netduma r3.

ping is fine inside game, when transfer happens from game into lobby that uses different ports.

not to mention when done with VPN there is no issue with reloading screens...

this video explains somehow the issue more complex https://youtu.be/mxKlTGTyw3w?si=X2NbQnbEdqWin4p_

Re: EE blocking ports externally

XRaySpeX — Wed, 04 Sep 2024 23:02:49 GMT

EE does not block outgoing ports.

Re: EE blocking ports externally

Baba_Jyaga — Thu, 05 Sep 2024 08:35:58 GMT

Let's assume you right why then in this case placing pc in the dmz helps and to top it up vpn connection also solves the issue, only when pure BT connection is used there is that issue please

Re: EE blocking ports externally

Ewan15 — Thu, 05 Sep 2024 09:13:19 GMT

Have you tried to establish whether the port is genuinely blocked?

This link should help you to do that

helpdeskgeek.com/networking/determine-open-and-blocked-ports/

Re: EE blocking ports externally

Baba_Jyaga — Thu, 05 Sep 2024 11:04:16 GMT

Will do that later once back home, and will post results. I have used some ps1 command and let it run for few minutes few days back and some port were blocked but prosses to complete would take possibly hrs and sadly I could finish it

Re: EE blocking ports externally

Baba_Jyaga — Thu, 05 Sep 2024 17:05:35 GMT

possibly leaking some info as i do but that's while game running:

C:\Windows\System32>Netstat -ab

Active Connections

Proto Local Address Foreign Address State
TCP 0.0.0.0:135 DK:0 LISTENING
RpcSs
[svchost.exe]
TCP 0.0.0.0:5040 DK:0 LISTENING
CDPSvc
[svchost.exe]
TCP 0.0.0.0:5357 DK:0 LISTENING
Can not obtain ownership information
TCP 0.0.0.0:49664 DK:0 LISTENING
[lsass.exe]
TCP 0.0.0.0:49665 DK:0 LISTENING
Can not obtain ownership information
TCP 0.0.0.0:49666 DK:0 LISTENING
EventLog
[svchost.exe]
TCP 0.0.0.0:49667 DK:0 LISTENING
Schedule
[svchost.exe]
TCP 0.0.0.0:49668 DK:0 LISTENING
[spoolsv.exe]
TCP 0.0.0.0:49706 DK:0 LISTENING
Can not obtain ownership information
TCP 0.0.0.0:49741 DK:0 LISTENING
[CNAB4RPD.EXE]
TCP 10.0.0.2:139 DK:0 LISTENING
Can not obtain ownership information
TCP 10.0.0.2:49675 20.90.153.243:https ESTABLISHED
UserManager
[svchost.exe]
TCP 10.0.0.2:49990 162-254-196-83:27029 ESTABLISHED
[Steam.exe]
TCP 10.0.0.2:50019 a2-23-205-133:https ESTABLISHED
[steamwebhelper.exe]
TCP 10.0.0.2:50020 a2-23-205-133:https ESTABLISHED
[steamwebhelper.exe]
TCP 10.0.0.2:50022 a104-82-234-109:https ESTABLISHED
[steamwebhelper.exe]
TCP 10.0.0.2:50023 81.134.111.57:https ESTABLISHED
[steamwebhelper.exe]
TCP 10.0.0.2:50048 162-254-196-67:27020 ESTABLISHED
[System]
TCP 10.0.0.2:50058 a5381c1ff1dd09563:40002 ESTABLISHED
[System]
TCP 10.0.0.2:50074 server-108-138-233-5:https ESTABLISHED
[System]
TCP 10.0.0.2:50076 server-108-138-233-5:https ESTABLISHED
[System]
TCP 10.0.0.2:50086 lhr25s32-in-f3:https ESTABLISHED
[steamwebhelper.exe]
TCP 10.0.0.2:50101 server-18-154-84-64:https TIME_WAIT
TCP 10.0.0.2:50106 server-108-138-233-5:https ESTABLISHED
[System]
TCP 10.0.0.2:50109 85.236.99.51:https TIME_WAIT
TCP 10.0.0.2:50114 server-108-138-233-5:https TIME_WAIT
TCP 10.0.0.2:50115 server-18-245-162-112:https ESTABLISHED
[System]
TCP 10.0.0.2:50116 server-18-245-143-101:https ESTABLISHED
[System]
TCP 127.0.0.1:27060 DK:0 LISTENING
[Steam.exe]
TCP 127.0.0.1:49985 DK:0 LISTENING
[Steam.exe]
TCP 127.0.0.1:49985 DK:50002 ESTABLISHED
[Steam.exe]
TCP 127.0.0.1:49986 DK:0 LISTENING
[Steam.exe]
TCP 127.0.0.1:49986 DK:50001 ESTABLISHED
[Steam.exe]
TCP 127.0.0.1:50001 DK:49986 ESTABLISHED
[steamwebhelper.exe]
TCP 127.0.0.1:50002 DK:49985 ESTABLISHED
[steamwebhelper.exe]
TCP 127.0.0.1:50045 DK:0 LISTENING
[System]
TCP [::]:135 DK:0 LISTENING
RpcSs
[svchost.exe]
TCP [::]:5357 DK:0 LISTENING
Can not obtain ownership information
TCP [::]:49664 DK:0 LISTENING
[lsass.exe]
TCP [::]:49665 DK:0 LISTENING
Can not obtain ownership information
TCP [::]:49666 DK:0 LISTENING
EventLog
[svchost.exe]
TCP [::]:49667 DK:0 LISTENING
Schedule
[svchost.exe]
TCP [::]:49668 DK:0 LISTENING
[spoolsv.exe]
TCP [::]:49706 DK:0 LISTENING
Can not obtain ownership information
TCP [::]:49741 DK:0 LISTENING
[CNAB4RPD.EXE]
UDP 0.0.0.0:3702 *:*
FDResPub
[svchost.exe]
UDP 0.0.0.0:3702 *:*
FDResPub
[svchost.exe]
UDP 0.0.0.0:5050 *:*
CDPSvc
[svchost.exe]
UDP 0.0.0.0:5353 *:*
Dnscache
[svchost.exe]
UDP 0.0.0.0:5355 *:*
Dnscache
[svchost.exe]
UDP 0.0.0.0:27015 *:*
[System]
UDP 0.0.0.0:27036 *:*
[Steam.exe]
UDP 0.0.0.0:50731 *:*
[BEService.exe]
UDP 0.0.0.0:50732 *:*
[System]
UDP 0.0.0.0:54728 *:*
Dnscache
[svchost.exe]
UDP 0.0.0.0:55389 *:*
FDResPub
[svchost.exe]
UDP 0.0.0.0:55665 *:*
[ExecPubg.exe]
UDP 0.0.0.0:61697 *:*
Dnscache
[svchost.exe]
UDP 10.0.0.2:137 *:*
Can not obtain ownership information
UDP 10.0.0.2:138 *:*
Can not obtain ownership information
UDP 10.0.0.2:27036 *:*
[Steam.exe]
UDP 127.0.0.1:64897 127.0.0.1:64897
iphlpsvc
[svchost.exe]
UDP [::]:3702 *:*
FDResPub
[svchost.exe]
UDP [::]:3702 *:*
FDResPub
[svchost.exe]
UDP [::]:54728 *:*
Dnscache
[svchost.exe]
UDP [::]:55390 *:*
FDResPub
[svchost.exe]
UDP [::]:61697 *:*
Dnscache
[svchost.exe]

dont know what it means tho 😞

Re: EE blocking ports externally

JimM11 — Thu, 05 Sep 2024 18:26:37 GMT

@Baba_Jyaga If i was you would try change to DNS server first.

Re: EE blocking ports externally

XRaySpeX — Thu, 05 Sep 2024 18:54:57 GMT

It means that they are all the incoming ports (Note they are associated with a Local Address) that all the processes on that PC are talking to (Established) or waiting for reply (Listening) on requests that the local processes have initiated. There is no mention of any blocked ports but by implication any ports not mentioned is currently unused & closed.

FYI: You'd be better using Netstat -abf to see what Foreign URL they are transacting with.

Re: EE blocking ports externally

Baba_Jyaga — Mon, 23 Sep 2024 19:38:29 GMT

found solution can be closed - had to scan ports and port forwarding rules helped

Re: EE blocking ports externally

JimM11 — Mon, 23 Sep 2024 19:44:06 GMT

@Baba_Jyaga Can you not expand are you leaving this as it is! Are EE at fault!!

Re: EE blocking ports externally

Baba_Jyaga — Wed, 25 Sep 2024 09:20:45 GMT

So I have scanned ports during the game run, and then started creating test rules on the router as port forward rules, and found out that if I do not enable this ports to be open i get problem if I do open them it's is super fast on top hit reg improved. So I can't conclude ee is at fault but it is them who route the traffic and in past upnp was enough to do all needed. Now for my gaming session I'm logging to router and enable rules for game once done disable them for some security

Re: EE blocking ports externally

bobpullen — Wed, 25 Sep 2024 12:02:49 GMT

Sounds like UPnP wasn't doing what you'd expect it to on the EE hub however, you seemingly had the same problem with a third-party Netduma router as well?

When you originally put the PC in the DMZ, did that also resolve the issue?

Re: EE blocking ports externally

Baba_Jyaga — Wed, 25 Sep 2024 12:14:02 GMT

So I have tried different router configuration one at the time bridge them etc. After which I have same result. So I settled for 3rd party as it helps with bufferbloat and ping.

When set onto dmz zone the problem was solved for pc that's where my suspicion has come of blocked port by ips and on top of that other that had similar issue have had it sorted by they provider by checking the traffic flow and identifying issue on those. But I can't leave pc in dmz as it is secure threat to my network so I rather open some target ports for short times of play time