[TelstraClear] TC blocking access to some ports?

Forums › One New Zealand (including Vodafone, WxC, Farmside) › [TelstraClear] TC blocking access to some ports?

timmmay

20575 posts

Uber Geek

Trusted

Lifetime subscriber

#14423 3-Jul-2007 00:27

I'm trying to connect from my US server to an instance of apache on my PC. When I run it on port 80 it's fine, but when I run it on port 90 I get an immediate "Connection refused" message. The firewall's open for both of these ports. Port 8000+ has the same problem.

Anyone know if TC blocks non-standard ports? Or any other ideas?

sneeble

29 posts

Geek

#76686 3-Jul-2007 00:53

I dont know enough but hey, try this

http://www.iana.org/assignments/port-numbers

inane

216 posts

Master Geek

Trusted

#76687 3-Jul-2007 01:04

what os?

timmmay

20575 posts

Uber Geek

Trusted

Lifetime subscriber

#76688 3-Jul-2007 01:08

I'm on XP pro. Obviously that makes no difference if TC is blocking the port, but it's more likely i'm doing something wrong... ideas welcome :)

freitasm

BDFL - Memuneh
79252 posts

Uber Geek

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#76693 3-Jul-2007 09:15

Interesting. I have some services running on my network here and I am able to access those when I run on port such as 8090 (note it's not the standard 8080).

I never had a problem like this...

inane

216 posts

Master Geek

Trusted

#76696 3-Jul-2007 10:12

i'm the same,

I can access a bunch of ports, I have a whole lot of services running in different places, and not on standard ports, no problems here.

Niel

3267 posts

Uber Geek

Trusted

#76697 3-Jul-2007 10:30

Maybe your router/modem blocking it? Perhaps it was reset to defaults?

You can never have enough Volvos!

michaeln

238 posts

Master Geek

Trusted

#76702 3-Jul-2007 10:47

TCL does NOT block ports.

Try running Wireshark on the PC (Ethereal) and seeing what's happening. Youll at least see the connection attempt coming in, assuming it is.

Is there any chance that the OUTGOING ports are being blocked at the machine trying to connect?

Equinox IT

Cloud spending continues to surge globally, but most organisations haven’t made the changes necessary to maximise the value and cost-efficiency benefits of their cloud investments. Download the whitepaper From Overspend to Advantage now.

timmmay

20575 posts

Uber Geek

Trusted

Lifetime subscriber

#76714 3-Jul-2007 12:36

My TC cable modem plugs into the Linksys 54GL router running the tomato firmware, so I don't think packet capture software will help - it's probably being blocked before it gets to the PC. I'm honestly stumped, I have no idea where the problems is. Windows firewall is off, and the router's set up as below. Ideas appreciated!

michaeln

238 posts

Master Geek

Trusted

#76718 3-Jul-2007 12:48

timmmay: My TC cable modem plugs into the Linksys 54GL router running the tomato firmware, so I don't think packet capture software will help - it's probably being blocked before it gets to the PC. I'm honestly stumped, I have no idea where the problems is. Windows firewall is off, and the router's set up as below. Ideas appreciated!

Well, it would help if only to prove that the connection is, or is not, getting through.

As a matter of interest, if you 'telnet 80' from the US server, what happens? Does the connection even get through, or is it blocked at the tcp level?

timmmay

20575 posts

Uber Geek

Trusted

Lifetime subscriber

#76719 3-Jul-2007 12:56

michaeln:
timmmay: My TC cable modem plugs into the Linksys 54GL router running the tomato firmware, so I don't think packet capture software will help - it's probably being blocked before it gets to the PC. I'm honestly stumped, I have no idea where the problems is. Windows firewall is off, and the router's set up as below. Ideas appreciated!

Well, it would help if only to prove that the connection is, or is not, getting through.

As a matter of interest, if you 'telnet 80' from the US server, what happens? Does the connection even get through, or is it blocked at the tcp level?

When I type telnet (my IP) 80 with no daemon running I get the message "trying..." and it eventually times out. If I try port 90 I get an immediate message saying

Trying 121.73.23.1...
telnet: connect to address 121.73.23.1: Connection refused
telnet: Unable to connect to remote host: Connection refused

I had a quick go at wireshark but i'll have to try again when I have a little more time to sit down with it.

michaeln

238 posts

Master Geek

Trusted

#76724 3-Jul-2007 13:48

timmmay: When I type telnet (my IP) 80 with no daemon running I get the message "trying..." and it eventually times out. If I try port 90 I get an immediate message saying

Trying 121.73.23.1...
telnet: connect to address 121.73.23.1: Connection refused
telnet: Unable to connect to remote host: Connection refused

I had a quick go at wireshark but i'll have to try again when I have a little more time to sit down with it.

Ah, are you SURE you meant 121.73.23.1? You haven't obfuscated your real address? That's the address of the gateway, not the address of your PC.

timmmay

20575 posts

Uber Geek

Trusted

Lifetime subscriber

#76726 3-Jul-2007 13:56

Well spotted! I copied and pasted the address wrong. The IP address is wrong, but the description is wrong, and good because I didn't want to post my IP anyway! :)

Port 80 with the right IP works, port 90 fails.

michaeln

238 posts

Master Geek

Trusted

#76727 3-Jul-2007 14:20

timmmay: Well spotted! I copied and pasted the address wrong. The IP address is wrong, but the description is wrong, and good because I didn't want to post my IP anyway! :)

Port 80 with the right IP works, port 90 fails.

I don;t suppose you have lft (Layer Four Traceroute) installed on the US server? That would tell you how far the connection was getting before it was blocked.

timmmay

20575 posts

Uber Geek

Trusted

Lifetime subscriber

#76752 3-Jul-2007 17:14

Nope, but i'll email tech support, hostgator are fantastic and will probably do it for me :)

timmmay

20575 posts

Uber Geek

Trusted

Lifetime subscriber

#76799 3-Jul-2007 20:40

I have the answer - the web host prevent outbound connections on non-standard ports. Thanks for the suggestion of the layer 4 traceroute, it wasn't done but they worked out the problem for me :)