Windows 2019 Failover Cluster setup

Question

I have created two Windows 2019 EC2 instances in the same vpc with the same security group and subnet. I am able to ping both instances from one another. However, while creating the Windows Failover cluster, I am unable to add the second node. I encounter the following error  
  
Failed to access remote registry. Ensure that the remote registry service is running and have remote administration enabled  
  
The remote registry service is running and the remote administration is enabled too. I have also assigned elastic IP addresses to both the instances. Both instances are able to communicate with the elastic IP. What could be the issue? How can I correct this problem? Any help will be appreciated.  
  
- Nitesh

nitaishonline · Answer

The issue is resolved now. I enabled all traffic access to the subnet group and that resolved the issue.

Ajeet-AWS · Answer

Hi,  
  
Thanks for updating the thread and sharing the resolution.  
  
Since the issue is already resolved by you, we can mark this thread as closed.

nitaishonline · Answer

I checked the event log of the server in which I am configuring the Windows Failover cluster. It shows the following log immediately after the addition of the secondary node fails.  
  
DCOM was unable to communicate with the computer xxx.xxx.xxx.xxx; requested by PID     1530 (C:\Windows\system32\mmc.exe), while activating CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820}. using any of the configured protocol. The CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} belongs to the Windows Management Instrumentation service.  
  
I hope this should help understand the cause and the resolution.

nitaishonline · Answer

The issue has been fixed by me. I have added the solution in the post.

Windows 2019 Failover Cluster setup

Add your answer

Relevant content