Bob Arning wrote:

> >As far as I can see, no connection is ever registered on the server. It
> >never gets to the handlePacket: loop where data is read from the socket,
> >and it does not sit waiting for data to appear on the socket in
> >handleConnection:. As far as I can see, the server never detects the
> >socket.
> 
> If I understand this correctly, the client thinks he has a connection (he would not have gotten to the W part otherwise), but the server appears not to be aware of the connection.

I think that seems to be the case too.

>I have seen behavior like this before and my best guess at what was happening in that case was that, prior to the current server being started, another listen on the same port wasn't properly cleaned up, leaving something in the OS accepting connections without passing them on to the current server. Two experiments might shed some light on this:
> 
> - When the problem is occurring, stop the current server and then see if a client can connect. I would try the connect a number of times in case it is an intermittent thing.

Well, the other client is also continously setting up connections and
killing them, and the server registers those just fine, so I suspect
that if there is still a 'dirty' port hanging around, the second client
would also hang. Correct, or am I missing something?

> - Does rebooting the server machine help?

Nope, it doesn't.

--
"You are more than the sum       Johan Fabry - Johan.Fabry at vub.ac.be
 of what you consume.            Vrije Universiteit Brussel
 Desire is not an occupation."   Programming Technology Lab, Room 10F709
  -- KMFDM                       Pleinlaan 2, 1050 Brussels, Belgium