Your config says: <attribute name="serverBindPort">4446</attribute> but the service is listening on 5446. That tells me you are using the ServiceBindingManager. For more on that see http://www.jboss.org/file-access/default/members/jbossas/freezone/docs/Se... You can look in docs/examples/binding-manager/sample-bindings, which is most likely where the 5446 is coming from. The AS 4.x SBM is fairly complex; in the the case of this Remoting Connect mbean it is using an XSL transform to alter the config. I can try to make some more detailed suggestions in a few days if you ping me. But not today or tomorrow, sorry. That's why I'm pointing you to the details. Only suggestion I can make now is look in that sample-bindings.xml for <service-config name="jboss.messaging:service=Connector,transport=bisocket" That configures a different remoting connector, and doesn't use an XSL transform to do it. The same approach could probably be applied to the "jboss.remoting:service=Connector,transport=socket" config as well. If your JBoss version doesn't have the "jboss.messaging:service=Connector,transport=bisocket" config in sample-bindings, you can see what I'm talking about at: http://anonsvn.jboss.org/repos/jbossas/branches/Branch_4_2/varia/src/reso... View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4229114#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...