Merged - Port blocking

rmg · 10-12-2003, 08:40

Can anyone confirm or deny if ntl are blocking the following ports

34518 and 34519 both on UDP

I called them Yesterday and was told that they are not blocking them but I am having loads of trouble with an app that uses them and have been informed on another forum that they are being blocked.

I would have asked on nthellworld.com but ntl seem to have killed it?

Thx.

--
rmg.

10-12-2003, 08:49

Quote:

Originally Posted by rmg

Can anyone confirm or deny if ntl are blocking the following ports

34518 and 34519 both on UDP

I called them Yesterday and was told that they are not blocking them but I am having loads of trouble with an app that uses them and have been informed on another forum that they are being blocked.

I would have asked on nthellworld.com but ntl seem to have killed it?

Thx.

--
rmg.

Sorry m8 we are not blocking these ports

Dooby · 10-12-2003, 09:07

what is the app? what setup do you have? ( i.e. directly connected, router, ICS anything like that? ) any kind of firewall?

rmg · 10-12-2003, 09:30

Hi, thanks for the confirm.

The app I am trying to run is called Xlink. It is a tunelling app for xbox that allows you to play system link games over the internet.

I am running through a router but have tried opening these ports and have even put the PC in the DMZ but still no luck.

The relevant threads are here

http://forums.xbox-scene.com/index.p...f=46&t=124238&

and here

http://forums.xbox-scene.com/index.p...f=46&t=134021&

Sounds like they are wrong tho?

--
rmg.

Dooby · 10-12-2003, 09:46

as i understand it, the only ports being blocked are those associated with viruses and security vulns...
and as far as the argument about 'making people pay for the gaming service'... if that was the case they would be blocking the XBox LIVE ports, not just the XBConnect type ones. If they are blocking them, the only reason i could think is because of the amount of data sent for things like XBC and XLink ( as in they are 'pretending' to the XBox that they are a 10Mb network, the xbox will chuck out loads of data )

have you looked in your router logs to check whether the PC is actually attempting to connect out? it may not be getting as far as the router.

Frank · 10-12-2003, 11:14

You should try our xbox forum instead

rmg · 10-12-2003, 12:07

is there a thread in there I can look at?

**Paul** · 10-12-2003, 20:38

Quote:

Originally Posted by rmg

...... I am having loads of trouble with an app that uses them and have been informed on another forum that they are being blocked.

That's nothing more than a guess on the part of whoever told you, it's not correct.

Mark W · 10-12-2003, 20:49

an update on the blocked ports.....

Quote:

the Narrowband, SACM Broadband and DTV Broadband Set-Top Box platforms have now had port blocking filters applied to Ports 137, 138, 139, 445, 593, 1433, 1434 & 27373.

10-12-2003, 21:00

Quote:

Originally Posted by Mark W

an update on the blocked ports.....

taken fron Nexus

kronas · 10-12-2003, 21:06

Quote:

Originally Posted by turbulentone

taken fron Nexus

and ? atleast hes informative instead of 'we dont block any other ports' even though new ones have been added to the block list

Mark W · 10-12-2003, 21:14

Quote:

Originally Posted by turbulentone

taken fron Nexus

so? they are blocked ports. if a customer called up and said "i cant use port 138", what are we supposed to do? lie and say thats nothing to do with ntl???

yes thats from nexus, but its accurate, to the point and relevant, so why waste time rewriting it?

**Paul** · 10-12-2003, 21:27

Quote:

Originally Posted by kronas

and ? atleast hes informative instead of 'we dont block any other ports' even though new ones have been added to the block list

What new ones ?

That looks like the original list (in fact, I believe they are blocking port 135 as well which is missing from that list).

kronas · 10-12-2003, 21:31

Quote:

Originally Posted by pem

What new ones ?

That looks like the original list (in fact, I believe they are blocking port 135 as well which is missing from that list).

i was not aware of 27373 being blocked

Myron · 11-12-2003, 23:22

Here is something that might be of slight interest. For anyone that's got a LinkSys router. I had a conflab with LinkSys recently and in the next firmware release for LinkSys routers there may be a workaround for blocked inbound ports. The ones that are uses as reply ports.

I beleive that there will be a facility where the user will be able to tell the router what short-term inbound reply ports not to use. Question is, when eill the next firmware update be made available.

Oh well.