In order for communication to take place, it does not suffice that a given endpoint is referencing in its options the DH server, but the DH server must be aware to be acting as such. So please verify the following
- If the DH server that the endpoints are pointing to is [email protected]<ip_or_name_of_dh>, please do
host [email protected]
and verify that the isdh flag is set to YES. If it is not, then please do
- Verify that the endpoints are pointing to the correct DH. To do this do, and one of the failing endpoints
and verify that in the options there is a DH entry pointing to the right DH, that is [email protected]
It is also very important to make sure that the DMS and DH are consistent. In the same way that the is_dh flag must be set to YES at the DH, we need to make sure that the is_dms is set to NO in the same DH database.
Conversely, any DMS machine must have the isdms flag to YES and the isdh flag to NO. You can verify that by doing
A common cause of errors is that the DMS has got the isdh and isdms both set to yes. That may prevent updates from being propagated to the subscribed DH and thus to be delivered to endpoints.
As a next step if the above does not help in resolving the problem, verify if stopping firewall services between ENTM and the endpoint helps to establish the communication. If stopping the firewall is not possible, refer to the product documentation and open the required ports in bi-directional mode.