This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(134.4, 22%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ER%3C/text%3E%3C/svg%3E)
Been struggling with creating a new failover cluster of servers, nodes are fresh, brand new installs of Windows Server 2022, A/D is Windows Server 2016 with that also as the functional level. I've tried the Failover GUI as well as New-Cluster PS cmd and both are failing at the same spot. I've ran validation on both hosts and fixed ALL errors. I've tried adding just 1 node, prestaging the CNO and even created an entirely new user to log into the server with and create the cluster. Tried creating a separate OU, as well as just letting it go into 'Computers' with same result. Verified connectivity and DNS is correct for all servers. Made sure to run Clear-Cluster cmd just to be safe. I've been through every Google search result 3 times over for error codes 1753, 234, etc. and keep coming up empty. Would love any other suggestions! I feel like it's something within Active Directory but unable to have any sort of epiphany as of yet.
The trace logs for Failover-Cluster show:
Got Domain DN 'DC=domain,DC=local' from DomainFlatName 'DOMAIN' or DomainNameDns 'domain.local'
GC does not have the object MYCLUSTERNAMEOBJECT."
Create cluster MYCLUSTERNAMEOBJECT will be using a Read-Write DC \DC.domain.local"
Searching for node object NODE1.domain.local failed. Error 234."
Creating Cluster name MYCLUSTERNAMEOBJECT in AD returned 234."
Couldn't resolve RPC binding to cluster 'IP.ADDRESS.OF.NODE1', Status = 1753"
The fail report generated shows:
Check whether the computer object MYCLUSTERNAMEOBJECT for node NODE1.DOMAIN.LOCAL exists in the domain. Domain controller \DC.DOMAIN.LOCAL.
Find a suitable domain controller for node NODE1.DOMAIN.LOCAL.
Check whether the computer object MYCLUSTERNAMEOBJECT for node NODE1.DOMAN.LOCAL exists in the domain. Domain controller \DC.DOMAIN.LOCAL. More data is available.
Bind to domain controller . More data is available.
Operation failed, attempting cleanup.
An error occurred while creating the cluster and the nodes will be cleaned up. Please wait...
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(57.599999999999994, 9%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJA%3C/text%3E%3C/svg%3E)
We are having the exact same issue with the same errors in the report output. Our servers are 2016 with a functional level of 2008. So this seems to be widespread. It should also be noted that we have an open case with Microsoft and have worked with them on this issue for the last week and they appear to be stumped as well.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(288, 6%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJS%3C/text%3E%3C/svg%3E)
Did you end up getting this resolved? I'm having the exact same issue and have tried all of the steps mentioned here as well. I've tried Server 2019 and 2022 with same results. Forest and domain functional levels are 2016 with DCs on 2016.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(230.39999999999998, 5%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ET%3C/text%3E%3C/svg%3E)
Hello
Having the same issue - any actual solution out there?
Postings going back to 2015 all offer tidbits - but I see even in 2023 we are fighting this issue.
BTW our next steps are to ensure Domain functional levels are raised to highest available and we are going to review / move our FSMO roles.
Spent hours myself researching this to no avail. Same issues on this thread as well. Functional level is my next step too but I have some work to get it up past 2016.