Ah. It turns out that org.jboss.remoting.samples.detection.jndi.ssl, and the facility it demonstrates, were created after the release of Remoting 2.0.0.GA, so you would have to find it them in the CVS repository. You could look in the HEAD branch, but the remoting_2_x branch is more reliable since that's where most active development is taking place. As for your problem, it should be fixed by those changes. In particular, the detector, just like your client, needs access to a truststore to be able to ping the server. Before JBREM-581: "can not do connection validation with ssl transport (only impacts detection)", there was no way to tell JNDIDetector about a truststore, but JNDIDetector now has a constructor public JNDIDetector(Map config); which allows the application to pass to the JNDIDetector the same truststore information that the client gets. By the way, for information about checking code out of the JBoss CVS repository, see http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossRemoting_source_and_build View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4024538#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...