remote question

From your laptop, can you ping for Cloverleaf server? Try using the full domain name name in the gui. Also try using the IP address.

Check for any firewalls between the two machines – Looks like your laptop can’t ‘see’ the Cloverleaf server.

Windows firewall on your laptop is obvious one to check but hopefully you’ve already enabled that correctly.

Is the server Windows or *nix – Again firewall, iptables etc.

Regards

Garry

This might not exactly solve your problem but I played with this bridge gap solution until I figured out how to get my service address on a HACMP cluster to work transparently.

In the $HCIROOT/server/server.ini file you can make an entry in the firewall block to tell the host server what IP and port to listen on.

I couldn’t find and example of the port number modification but here is what I could locate in an old email from Gotham about setting the IP

[firewall]

rmi_exported_server_port=10.145.13.51

If I recall I did try it and got it to work but don’t remeber if the sytanx is exactly right on this particualr email.

Being you have 2 separate IP access points that might be insulated from the other this might not be as helpful as it would be for a HACMP situation that I had used it for.

However, it might be worth knowing this trick in the event there is a way to use it to help you.

You could at least try it to see if each IP on the separate NICs can independently provide access to the host server even though both NICs might not provide simultaneous hostserver access.

If the underlying behaivor of the hostserver only allows access via a specified IP then you may still be forced to choose one or the other but now at least you might have a choice.

What is going in needs to match what’s going out.

So, since your client.ini is configured for:

[firewall]

rmi_exported_server_port=”172.20.128.23″

You need to initiate your connection with ip 172.20.128.23 or a dns name that points to that ip.

Start by connecting to 172.20.128.23 instead of a host name in the “Select the Host on which to contact the Server” box.

What you are probably dealing with is the a WAN IP versus a LAN IP.  In the server.ini you want to have the host server listening on the WAN IP (in your case 172.20.128.23).  In your hosts file you need to have the hostname mapped to the internal IP (172.20.133.228).  This is because you make the connection to the WAN IP but cloverleaf then “talks to itself” using the LAN IP.

In other words, it sounds like your server.ini is set up right but your /etc/hosts file does not have an entry that points your LAN IP to the hostname.  You can determine whether this is the case by accessing your box via telnet or ssh and attempting to ping your hostname.  If the ping tries to hit the WAN IP instead of the LAN IP then you need to modify your hosts file.

Looking back through I see that the server is a windows server so the host file is going to be different than /etc/hosts.  I believe the solution is still applicable but the location of the host file is different (and I don’t make any claim to knowing the nuances involved with the hosts file in windows, I will be interested to see what configuration was finally able to work with this).