Public and Private cluster traffic mixing

We have 3 servers in a cluster.

all 3 have 2 NIC

Each NIC is configured with 1 IP/ public / private lan respectively.

The private lan NICs are connected to a hub. They can ping each other over their respective IP addresses.

The server document contains explicit IP address for both ports:

TCPIP/ CLUSTER. Both ports are enabled for all servers.

Server_Default_Cluster_Port = cluster is set for all 3 servers via configuration documents. (one for each server obviously)

The notes ini files on each server do contain the correct IP ranges ports etc.

server 1/2 commincate with no issue and only show private traffic on their cluster port.

server 3 cannot communicate with itself on the cluster port (the other two do have entries for self checking)

Server 3 only connect to Server 2 from Public Port (server3) to private port (server2)

so, somewhere, the OS must be bridging the network.

On the private NICs, I have disabled MS sharing/MS client. Run straight TCPIP with no netbios enabled.

No host records.

any ideas?

I must reiterate though, the admin help is spot on for the other two servers… They work flawlessly, just not the 3rd…

Subject: Public and Private cluster traffic mixing …

Have you configured _TCPIPAddress in the notes.ini for each configured domino port? (see the admin help db, notes.ini settings).

Is the private cluster port listed first in the Ports= line in the notes.ini?

Can server3 ping server2 on the private port?

Is there a connection document enabled on the private port (even without scheduled replication and/or mail params) between server3 and server2?

If you perform any changes to the notes.ini via the admin client (or set config commands) it may be necessary to stop and start domino in order for these changes to be effective! (Try first stopping and starting the individual ports).

Hope this helps,

Ben

P.S. It is recommended that explicit IP Addresses not be used in the server document. Instead use DNS names.

P.P.S The first line in the server document should contain the public port (clients will use this for resolution). The second line should contain the private port details.