Hi Ian, Actually, in general it wouldn't make sense in Remoting to specify the local address of a connection because a single connection will typically use multiple sockets. For example, the socket transport will create a pool of sockets, and, presumably, HttpURLConnections, which are used by the Remoting http transport, do the same under the covers. However, you should take a look at the "bisocket" transport, which was created to work around firewall restrictions in the sense that all connections are created from the client to the server. In particular, if you have callbacks sent from the server to the client, the TCP connection is made from a client socket on the client to a server socket on the server. For more information, see Section 5.4.16 "Bisocket invoker" in the Remoting Guide (http://labs.jboss.com/jbossremoting/docs/guide/ch05.html#d0e2629). -Ron View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4057237#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...