Do NTL block port 113 (ident) ?

cake99 · 13-03-2005, 10:09

Hi, I've set up an ident server on my broadband connection. However, I cant seem to connect to it from anywhere on the internet. I tried just running a listen server on port 113, and connecting to that, and i get

tcpconnect: Can't connect to server: No route to host

I tried it with other ports and they all seem to get through, its just port 113 that doesnt. Which leads me to ask, does NTL block port 113, or am I doing something silly and wrong (which could be the case, especially at this time of the morning lol)

I cant really see any logical reason to block it, ident is harmless and all other ports I tried are open.

cheers

chrisb123 · 13-03-2005, 10:10

http://www.ntlworld.com/tunnel.php?task=portBlocking

cake99 · 13-03-2005, 10:25

port 113 isnt in that list, is it confirmed that they are blocking it (I noticed it said they would add more if they were used by worms etc)

13-03-2005, 10:47

Quote:

Originally Posted by cake99

Hi, I've set up an ident server on my broadband connection. However, I cant seem to connect to it from anywhere on the internet. I tried just running a listen server on port 113, and connecting to that, and i get

tcpconnect: Can't connect to server: No route to host

I tried it with other ports and they all seem to get through, its just port 113 that doesnt. Which leads me to ask, does NTL block port 113, or am I doing something silly and wrong (which could be the case, especially at this time of the morning lol)

I cant really see any logical reason to block it, ident is harmless and all other ports I tried are open.

cheers

As far as i am aware we "NTL" do not block port 113

Graham M · 13-03-2005, 11:40

No they dont otherwise my IRC server wouldnt be working properly (which it is)

Toto · 13-03-2005, 14:07

I can confirm they do not block port 113, I am on IRC at the moment

Graham M · 13-03-2005, 14:45

Some IRC servers require IDENT to allow you to connect, those that dont would just take a VERY long time to connect

cake99 · 14-03-2005, 00:46

After a sleep and another look, I realised it was something I was doing wrong

Thanks everyone for your help :-)

Badders · 14-03-2005, 14:04

From the link:

Quote:

The ports being blocked (inbound only, to stop infections) are: 137 (UDP), 138 (UDP), 139 (TCP), 445 (UDP & TCP), 593 (TCP), 1433 (TCP), 1434 (UDP), 27374 (TCP)

I'm sure my Router is reporting dozens of inbound blocks to ports 445,1433,1434.

Can anyone explain what I'm seeing?

AdrianC · 14-03-2005, 15:10

I believe that the ports are only blocked into NTL's network, therfore the traffic you are seeing and blocking originates within NTL's network already.

Badders · 14-03-2005, 15:21

OK, that makes sense. I'll check the blocked IP's tonight. Thanks.