From: Rusdi (rusdi@komputeralif.com)
Date: Sat Oct 05 2002 - 05:08:00 EDT
Dear fellow members!
I need your help for solving problem on my trucluster v 1.6 ( Production
Server)
The problem as follows;
If the 'service' is in 1st server, I don't have any problem
for connecting to cluster server ( hmsfclu) either via LAN or WAN
i.e.: Can do ping to 129.0.2.18 or to 129.0.2.20 (cluster's ip).
However, if I move the 'service' to 2nd server we only can
connect to 'cluster' ( 129.0.2.20 ) via LAN and can not make
connection to 'cluster' (129.0.2.20) via WAN.
When 'cluster service' on 1st Server
LAN:
1. Ping to IP address of 1st server (129.0.2.18) ---> OK
2. Ping to IP address of 2nd server (129.0.2.19) ---> OK
3. Ping to IP address of hmsfclu : 129.0.2.20 ----> OK (cluster's
IP)
WAN ( from heliport, via router):
1. Ping to IP address of 1st server (129.0.2.18) ---> OK
2. Ping to IP address of 2nd server (129.0.2.19) ---> OK
3. Ping to IP address of hmsfclu : 129.0.2.20 ----> OK
==========================
When 'cluster service' on 2nd Server
LAN:
1. Ping to IP address of 1st server (129.0.2.18) ---> OK
2. Ping to IP address of 2nd server (129.0.2.19) ---> OK
3. Ping to IP address of hmsfclu : 129.0.2.20 ----> OK
WAN ( from heliport, via router):
1. Ping to IP address of 1st server (129.0.2.18) ---> OK
2. Ping to IP address of 2nd server (129.0.2.19) ---> OK
3. Ping to IP address of hmsfclu : 129.0.2.20 ----> NOT OK (KO)
Note: We implement DNS server in our computer environment.
Thank you in advance for your help,
Rusdi
rusdi@komputeralif.com
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:48:55 EDT