Martin Malina created JBIDE-12352: ------------------------------------- Summary: Remote connection to servers cannot be established with IPv6 Key: JBIDE-12352 URL: https://issues.jboss.org/browse/JBIDE-12352 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.1 Environment: JBDS 5.0.1 Fedora 17 32bit OpenJDK 1.6 Reporter: Martin Malina Assignee: Rob Stryker Fix For: 3.3.2, 3.4.x After creating JBIDE-12351 for JMX connection, I found out that the connection cannot be established at all - even when you don't try to connect via JMX. When you set up a remote as7/eap6 server accessible over IPv6 and start the server, the remote connection will fail with this error: {code} Jul 20, 2012 3:14:57 PM org.xnio.Xnio <clinit> INFO: XNIO Version 3.0.3.GA Jul 20, 2012 3:14:57 PM org.xnio.nio.NioXnio <clinit> INFO: XNIO NIO Implementation Version 3.0.3.GA Jul 20, 2012 3:14:57 PM org.jboss.remoting3.EndpointImpl <clinit> INFO: JBoss Remoting version 3.2.7.GA Jul 20, 2012 3:15:46 PM org.jboss.remoting3.remote.RemoteConnection handleException ERROR: JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed Jul 20, 2012 3:15:46 PM org.jboss.remoting3.remote.RemoteConnection handleException ERROR: JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed Jul 20, 2012 3:15:51 PM org.xnio.Xnio <clinit> INFO: XNIO Version 3.0.4.GA-redhat-1 Jul 20, 2012 3:15:51 PM org.xnio.nio.NioXnio <clinit> INFO: XNIO NIO Implementation Version 3.0.4.GA-redhat-1 Jul 20, 2012 3:15:51 PM org.jboss.remoting3.EndpointImpl <clinit> INFO: JBoss Remoting version 3.2.8.GA-redhat-1 Jul 20, 2012 3:15:52 PM org.jboss.remoting3.remote.RemoteConnection handleException ERROR: JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira