I have a problem getting my RMI application to work. Having a RMI Server app running in a VMWare that forwards port 1099 in a NAT enviroment.
Physical machines IP on the outside = 184.108.40.206
Physical machines IP in local area = 192.168.0.1
Virtual machines IP = 192.168.0.100
I start a rmiregistry on my virtual machine and since port 1099 is NAT-forwarded I can connect to the registry from the outside using telnet 220.127.116.11:1099.
I startup my serverside rmi-app on the virtual machine
and in my app I do the following binding:
This work fine with HOST=127.0.0.1 or HOST=192.168.0.100 but when setting HOST=18.104.22.168 (the public IP address), startup fails with:
Registry reg = LocateRegistry.createRegistry Registry.REGISTRY_PORT);
Naming.rebind("//"+ HOST + ":1099/" + CommandBroker.NAME, this);
When server is running with HOST=127.0.0.1 or HOST=192.168.0.100 (like I said using HOST=22.214.171.124 doesn't work at all, the server is not allowed to bind) the binding from the outside using my client-app works (bind to 126.96.36.199 the public IP) , but however when trying to actually use the remote object the client throws the following exception:
java.rmi.AccessException: Registry.Registry.rebind disallowed; origin /188.8.131.52 is non-local host
Using HOST=127.0.0.1 on serverside
or when server HOST=192.168.0.1
Operation timed out: connect:could be due to invalid address
I assume using the public IP on serverside by setting HOST= to 184.108.40.206 is the right way, but as stated above binding to the rmiregistry is not allowed! What am I missing?
java.net.ConnectException: Connection refused: connect
Thanks alot, your help is very much appreciated.