Access Denied trying to connect to a cluster with Failover Cluster Manager Exchange 2010

Question

The issue where you can connect to the Failover Cluster Manager on iphmail04 but not on iphmail02, despite using the same credentials, points to a localized issue on iphmail02

Answer 1

Hello, @SATISHKUMAR A/L PANNIRSELRAM,

Welcome to the Microsoft Q&A platform!

Based on your description, you're encountering an issue with connecting to the Failover Cluster Manager on certain nodes (iphmail04 and iphmail02) while using the same credentials. This issue could be due to permissions or configurations specific to the nodes in your cluster.

Here are a few steps you can take to troubleshoot and resolve this issue:

1.Check Permissions: Ensure that the account you're using has the necessary permissions on both nodes. Sometimes, permissions might be set differently on each node.

2.Validate Cluster Configuration: Use the Failover Cluster Manager to run a validation test on the cluster. This can help identify any configuration issues.

3.Review Event Logs: Check the event logs on both nodes for any errors or warnings that might give more insight into why access is being denied.

4.Network Configuration: Verify that the network settings are consistent across all nodes. Differences in network configuration can sometimes cause connectivity issues.

5.DCOM Settings: Ensure that the Distributed Component Object Model (DCOM) settings are correctly configured. Inconsistent DCOM settings can lead to access issues.

6.Patch Levels: Make sure that all nodes are running the same patch level. Inconsistent patch levels can cause nodes to fail to join the cluster.

7.DNS Resolution: Ensure that all nodes can properly resolve each other’s DNS names. This is crucial for cluster communication.

8.Version Compatibility: Confirm that all nodes are running compatible versions of the Windows Server and Exchange Server software.

In addition, here is a case study similar to your issue for your reference: https://learn.microsoft.com/en-us/answers/questions/2038197/access-denied-trying-to-connect-to-a-cluster-with.

Should you need more help on this, you can feel free to post back. 

---

If the answer is helpful, please click on ACCEPT ANSWER as it could help other members of the Microsoft Q&A community who have similar questions and are looking for solutions.

Thank you for your support and understanding.

Best Wishes,

Alex Zhang

Answer 2

Hi AlexI would like to inform that the exchange server is running 20101.Check Permissions:

Answer : With the same permission , able to connect iphmail04 but unable to connect iphmail02.

2.Validate Cluster Configuration: Use the Failover Cluster Manager to run a validation test on the cluster. This can help identify any configuration issues.

Answer: how i can do this >

3.Review Event Logs: Check the event logs on both nodes for any errors or warnings that might give more insight into why access is being denied.

Answer: There is no any error or critical logs. Event ID 2050 and Event ID 2051 (but both server have the same event id which shows there is no any issue can find from event logs)

4.Network Configuration: Verify that the network settings are consistent across all nodes. Differences in network configuration can sometimes cause connectivity issues.

Answer: how i can do this ?

5.DCOM Settings: Ensure that the Distributed Component Object Model (DCOM) settings are correctly configured. Inconsistent DCOM settings can lead to access issues.

6.Patch Levels: Make sure that all nodes are running the same patch level. Inconsistent patch levels can cause nodes to fail to join the cluster.

Answer: there is no patchinh

7.DNS Resolution: Ensure that all nodes can properly resolve each other’s DNS names. This is crucial for cluster communication.

Answer: Yes done

8.Version Compatibility: Confirm that all nodes are running compatible versions of the Windows Server and Exchange Server software.

Answer: Same version for both