Hello! If your client tries to connect to your server and server sees this as traffic from 168.63.129.16, unfortunately that won't work.
Intra-cluster Ignite connections can be reversed (it is not a client-server protocol rather than server-server), this means that connections should come from the addressed that node would advertise, and it is possible to open this connection in other direction. It won't work if external client connects from 168.63.129.16 but when you connect to 168.63.129.16 you don't see this client there. You should make sure all nodes make use of internal addresses, such as 10.0.0.x. Regards, -- Ilya Kasnacheev 2018-05-10 20:40 GMT+03:00 JP <[email protected]>: > Please check this > https://blogs.msdn.microsoft.com/mast/2015/05/18/what-is- > the-ip-address-168-63-129-16/ > > That ip belongs to Azure > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
