On some installations users might encounter the problem that the GECAMed Client is only working on the same machine the GECAMed server is installed on. When trying to start the client on an other machine, it will refuse to start or the login will not work.

The problem is caused by a wrong or not working DNS configuration of the GECAMed server. Meaning, the server retrieves its own hostname configures in the operating system. It then does a DNS lookup for that hostname. The retrieved IP is then used to bind the JBoss Remoting Interface (RMI).

If the hostname is resolved to to a local address like 127.0.x.x the RMI Interface will not be reachable from outside the server itself. The hostname needs to be resolved to the real, route-able IPv4 address of the machine (often like 192.168.x.x)

Please try the following steps to diagnose the problem and get the needed information:

1. Open a command shell ON YOUR GECAMED SERVER (CMD.exe on windows, Terminal on OSX)
2. Type hostname and press Enter, That will show you the hostname of your GECAMed Server.
3. Type ping followed by the hostname, That will show you the IP address your hostname is resolved to.
4. If that address is different from the real ip address of your server, you need to fix your DNS lookup.

Make the server's IP address static and declare it in its own hosts file instead of 127.0.1.1

remove the following line if it exits

 127.0.1.1 gecamed-server-name

add the following line

 192.168.x.x gecamed-server-name

Where 192.168.x.x is the real IP address of your GECAMed server and gecamed-server-name is the hostname of your machine.

You can find the hosts file at:

• Windows: C:\Windows\System32\drivers\etc
• Linux/OSX: /ets/hosts

hosts file needs to be edited with Admin/root rights.