954250 wrote:does the exception come from the "getRegistry()" call or "rebind()"? generally, include all exception details when asking for help.
rmiregistry seems to find the remote classes now, Thanks!!!
however new exception thrown:
exception: java.rmi.ConnectException: Connection refused to host: 192.168.56.1; nested exception is:
java.net.ConnectException: Connection refused: connect
exception occurs when running the server class at line:
Also note, the "java.policy" file has been updated with RMI server permission allowing permission to the path where the classes are located
EJP wrote:good to know. i thought it might try to establish some initial connection.
It won't come from the getRegistry() call: that doesn't do any network operations.
@OP: That means the Registry isn't running.it could also mean that the registry is not bound to the correct network interface (e.g. bound the localhost "127.0.0.1" instead of the external ip "192.168.56.1").
EJP wrote:thanks, i obviously didn't check the docs before writing that original response.From the Javadoc: "Note that a getRegistry call does not actually make a connection to the remote host.".It won't come from the getRegistry() call: that doesn't do any network operations.good to know. i thought it might try to establish some initial connection.