On Saturday, 28 September 2013 at 23:25:20 UTC, Kapps wrote:
This is just a guess, but it is because you're setting the socket to be blocking after the call to accept? If it defaults to non-blocking, this would cause accept to return immediately, so the client connecting would fail as the server isn't currently accepting connections. Also to verify it's not a firewall issue, for connecting try using 127.0.0.1.
Thank you for your reply:) Seeing your reply, I try commenting "client.blocking(true)" out, but it do not work. My server and client do work using 127.0.0.1, So ,maybe I think firewall setting is correct.
