Not fully about the issue listed above. But I had an issue a bit similar. My messaging setup was working locally. But over a network , my client wasn't able to establish a connection with my server. With lots of googling, trial and error and with help from a friend , I got it working by following these steps : * In jboss-5.0.0\server\default\conf\jndi.properties added : java.naming.provider.url=192.168.0.116:1099 * Changes to jboss-5.0.0\server\default\deploy\messaging\jms-ds.xml Avoided using ${jboss.bind.address} : The value substitution wasn't appearing in this file. DefaultJMSProvider2 org.jboss.jms.jndi.JNDIProviderAdapter <!-- The combined connection factory --> java:/XAConnectionFactory <!-- The queue connection factory --> java:/XAConnectionFactory <!-- The topic factory --> java:/XAConnectionFactory <!-- Uncomment to use HAJNDI to access JMS--> java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces java.naming.provider.url=192.168.0.116:1099 <tx-connection-factory> <jndi-name>JmsXA2</jndi-name> <xa-transaction/> <rar-name>jms-ra.rar</rar-name> <connection-definition>org.jboss.resource.adapter.jms.JmsConnectionFactory</connection-definition> <adapter-display-name>JMS Adapter</adapter-display-name> <config-property name="SessionDefaultType" type="java.lang.String">javax.jms.Topic</config-property> <config-property name="JmsProviderAdapterJNDI" type="java.lang.String">java:/DefaultJMSProvider2</config-property> <security-domain-and-application>JmsXARealm2</security-domain-and-application> jboss.messaging:service=ServerPeer </tx-connection-factory> Corresponding changes to jboss-5.0.0\server\default\conf\login-config.xml: <application-policy name="JmsXARealm2"> <login-module code="org.jboss.resource.security.ConfiguredIdentityLoginModule" flag="required"> <module-option name="principal">guest</module-option> <module-option name="userName">guest</module-option> <module-option name="password">guest</module-option> <module-option name="managedConnectionFactoryName">jboss.jca:service=TxCM,name=JmsXA2</module-option> </login-module> </application-policy> * Bound the address during jboss's startup run.bat -b 192.168.0.116 * Changed the firewall settings on my XP machine to allow my client to interact with my server. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4227469#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...