Connection between runtime client and app server

This should help. softwareforums.aveva.com/.../failure-to-deploy-winplatform-runtime-node-to-galaxy

This should help. softwareforums.aveva.com/.../failure-to-deploy-winplatform-runtime-node-to-galaxy

1-I checked the bootstrap service and it's running

2-change network account and put the same domain and user 

what can I do more to solve this issue ?

Hazem Mohamed In the link shared above I have listed 3 possibilities and aabootstarp service is not running on the remote node is one of them. Have you verified on other 2 possibilities as well?

1. The aabootstrap service on the remote node is not running.
2. The remote  node node has a older version of the product.
3. The hostname resolution for the remote node has some issue and resolving to the different IP where the product is not installed.

The 2 item is obvious and you can confirm this by just looking at the aabootstrap version on the remote node. To verify on the 3rd possibility, check the OCMC logs on the GR node, when you start deploying the platform. There should be a message indication hostname to IP resolution. Then you can confirm if the IP is pointing to the correct remote machine.