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.

On Sun, 29 Sep 2013 03:47:27 +0200, wagtail wrote:

> When my server and client are on the same machine,these succeed.
> If I try communicating with other machine via global network,it do not
> work.
> IP of my server which you say above should set to server side?

When you instantiate your InternetAddress class, set it to the assigned IP of your server machine.

It's starting to look like more of a network configuration problem and not a D.learn problem. I'd rather not pollute this forum with those type of issues. Good luck.

On Sunday, 29 September 2013 at 15:25:53 UTC, ollie wrote:
> When you instantiate your InternetAddress class, set it to the assigned
> IP of your server machine.
>
> It's starting to look like more of a network configuration problem and
> not a D.learn problem. I'd rather not pollute this forum with those
> type of issues. Good luck.

I'll do my best.

Thank you.