Trouble initiating a TCP connection in Python--blocking and timing out

Question

For a class project I'm trying to do some socket programming Python but running into a very basic issue. I can't create a TCP connection from my laptop to a lab machine. (Which I'm hoping to use as the "server") Without even getting into the scripts I have written, I've been simply trying interpreter line commands with no success. On the lab machine (kh4250-39.cselabs.umn.edu) I type the following into Python:

from socket import *
sock = socket()
sock.bind(('', 8353))
sock.listen(5)
sock.accept()

And then on my laptop I type:

from socket import *
sock = socket()
sock.connect(('kh4250-39.cselabs.umn.edu', 8353))

At which point both machines block and don't do anything until the client times out or I send a SIGINT. This code is pretty much exactly copied from examples I've found online and from Mark Lutz's book Programming Python (using '' for the server host name apparently uses the OS default and is fairly common). If I run both ends in my computer and use 'localhost' for the hostname it works fine, so I suspect it's some problem with the hostnames I'm using on one or both ends. I'm really not sure what could be going wrong on such a simple example. Does anyone have an idea?

Maybe there is a packet filter or something like this involved. — glglgl
– glglgl, Commented Oct 19, 2011 at 20:08

jathanism · Accepted Answer · 2011-10-19 21:27:51Z

1

A good way to confirm whether it's a firewall issue or not is to perform a telnet from the command-line to the destination host in question:

% telnet kh4250-39.cselabs.umn.edu 8353
Trying 128.101.38.44...

And then sometime later:

telnet: connect to address 128.101.38.44: Connection timed out

If it just hangs there at Trying and then eventually times out, chances are the connection to the remote host on that specific port is being blocked by a firewall. It could either be at the network layer (e.g. a real firewall or a router access-list) or at the host, such as iptables or other host-based filtering mechanisms.

Access to this lab host might only be available from within the lab or the campus network. Talk with your professor or a network administrator or someone "in the know" on the network to find out for sure.

answered Oct 19, 2011 at 21:27

jathanism

33.9k9 gold badges72 silver badges89 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

gecco · Accepted Answer · 2011-10-19 21:12:19Z

0

Try to bind the server to 'kh4250-39.cselabs.umn.edu' instead of '':

sock.bind(('kh4250-39.cselabs.umn.edu', 8353))

If this does not work: Another reason could be a firewall blocking the port 8353....

answered Oct 19, 2011 at 21:12

gecco

19k11 gold badges53 silver badges68 bronze badges

1 Comment

user207421 Over a year ago

The specific bind address won't help. He's binding to INADDR_ANY now.

Collectives™ on Stack Overflow

Trouble initiating a TCP connection in Python--blocking and timing out

2 Answers 2

Comments

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related