Binding Client/Server with a Dedicated IP
Client/server can be bound with a dedicated IP address in the following way:
Right click on a server IP address under Server Nodes in Cache Explorer and click on Select NIC option.
Available Network Interface Cards dialog will open. It will list all network cards available on that node with their assigned IP addresses.
Select the Client/Server option from drop down in front of the IP with which you want to bind the client and server.
NCache will ask for confirmation to apply configuration and restart service. Click Yes.
At this stage, NCache might ask for credentials if the node is remote or does not have the rights.
If the node belongs to the same domain, provide the Username and Password.
If the node does not belong in the same domain, add the user to the Administrator group in Windows and then provide the username as
domainname\usernameand the password.
This restarts the NCache service to use the selected IP addresses for the specified communication (client-server).
If you have dedicated network cards configured for public and private communication, then you might not be able to create new clusters or possibly existing NCache cluster could not communicate with others. Please note, the following problems will occur if nodes are unable to communicate with each other on specific interface(s).
NCache Service starts at one interface whereas other nodes try to communicate with it on the other interface. Therefore the two nodes are always unable to communicate with each other even when apparently both nodes are fully functional.
NCache Clients connect to NCache Server to get OutProc cache instances. So, it is possible that NCache Server starts at one interface whereas the client tries to connect to it on the other interface. This way, though NCache Server is ready to accept the client requests, client applications will always be unable to connect to the OutProc caches.
Situations can arise where cluster nodes are unable to join with each other and no cluster is forming. The reason could be that one node is listening join requests from other nodes on one network interface whereas other nodes send join requests on other network interface.
To avoid such problems, you can bind NCache service to specific IP that is publicly available to other nodes in the cluster.
<add key = "NCacheServer.BindToClientServerIP" value = "<your-ip>" />