Thanks, Val. Running the servers with the property set resolved my problem.
I see that this is already anticipated in the ignite.sh script. I only had to uncomment the line with this property. Roger -----Original Message----- From: vkulichenko [mailto:valentin.kuliche...@gmail.com] Sent: Thursday, July 06, 2017 2:53 PM To: user@ignite.apache.org Subject: Re: Unable to connect from Windows Java client to Linux server cluster (ignite 2.0.0) Hi Roger, This is a known issue: https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_browse_IGNITE-2D5189&d=DwICAg&c=IL_XqQWOjubgfqINi2jTzg&r=1esZO0r0bYS90lcsaLA6N4AFxuNo6lzauhETGwdJQoQ&m=zrWGK7PfNr8lHLPVvqtrgWoTZ4aXZ1RfaTzoNWdnrOY&s=S99xvOqo1iLdlOVR2ynj-5GzFQMoVcUdrqdqFLw4IUw&e= Try to set java.net.preferIPv4Stack=true system property. -Val -- View this message in context: https://urldefense.proofpoint.com/v2/url?u=http-3A__apache-2Dignite-2Dusers.70518.x6.nabble.com_Unable-2Dto-2Dconnect-2Dfrom-2DWindows-2DJava-2Dclient-2Dto-2DLinux-2Dserver-2Dcluster-2Dignite-2D2-2D0-2D0-2Dtp14410p14421.html&d=DwICAg&c=IL_XqQWOjubgfqINi2jTzg&r=1esZO0r0bYS90lcsaLA6N4AFxuNo6lzauhETGwdJQoQ&m=zrWGK7PfNr8lHLPVvqtrgWoTZ4aXZ1RfaTzoNWdnrOY&s=a8JLoBf3757j9EcXXvzQi2SsY6QkLBuSDtF0XrSSitE&e= Sent from the Apache Ignite Users mailing list archive at Nabble.com.
