Can't connect to Hyper-V Converged Cluster

%3CLINGO-SUB%20id%3D%22lingo-sub-654551%22%20slang%3D%22en-US%22%3ECan't%20connect%20to%20Hyper-V%20Converged%20Cluster%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-654551%22%20slang%3D%22en-US%22%3E%3CP%3EI've%20raised%20a%20bug%20here%20-%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fwindowsserver.uservoice.com%2Fforums%2F295071-management-tools%2Fsuggestions%2F37729852--bug-can-t-connect-ti-hyper-v-converged-cluste%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwindowsserver.uservoice.com%2Fforums%2F295071-management-tools%2Fsuggestions%2F37729852--bug-can-t-connect-ti-hyper-v-converged-cluste%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20installed%20Windows%20Admin%20Center%20with%20high%20availability%20following%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-server%2Fmanage%2Fwindows-admin-center%2Fdeploy%2Fhigh-availability%22%20rel%3D%22noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-server%2Fmanage%2Fwindows-admin-center%2Fdeploy%2Fhigh-availability%3C%2FA%3E.%3C%2FP%3E%3CP%3EI%20can%20connect%20to%20nodes%20in%20the%20cluster%20fine%20through%20WAC%2C%20however%20when%20I%20try%20to%20add%20the%20cluster%20it%20says%20it%20can't%20find%20the%20name.%3C%2FP%3E%3CP%3EIf%20I%20click%20on%20one%20of%20the%20nodes%20it%20gives%20the%20FQDN%20of%20the%20cluster%2C%20I%20click%20it%20and%20it%20adds%20it%20as%20a%20connection%20but%20when%20I%20try%20to%20access%20it%2C%20it%20complains%20that%20WINRM%20couldn't%20not%20process%20the%20operation.%3C%2FP%3E%3CP%3EI've%20tried%20it%20with%20two%20different%20clusters%20on%20our%20network.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20ideas%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-654551%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Ecluster%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EConverged%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EHyper-V%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWAC%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWindows%20Admin%20Center%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-657793%22%20slang%3D%22en-US%22%3ERe%3A%20Can't%20connect%20to%20Hyper-V%20Converged%20Cluster%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-657793%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F350954%22%20target%3D%22_blank%22%3E%40CyclopsHelpdesk%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20checked%20and%20the%20cluster%20IP%20that%20is%20on%20a%20node%20is%20showing%20as%20listening%20on%20that%20IP%20when%20running%20winrm%20e%20winrm%2Fconfig%2Flistener%20in%20PowerShell%20-%20so%20that%20doesn't%20seem%20to%20be%20the%20issue.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-657868%22%20slang%3D%22en-US%22%3ERe%3A%20Can't%20connect%20to%20Hyper-V%20Converged%20Cluster%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-657868%22%20slang%3D%22en-US%22%3EDeleting%20the%20listener%20and%20recreating%20it%20fixed%20the%20issue.%3CBR%20%2F%3E%3CBR%20%2F%3EIn%20PowerShell%3A%3CBR%20%2F%3Ewinrm%20delete%20winrm%2Fconfig%2FListener%3FAddress%3D*%2BTransport%3DHTTP%3CBR%20%2F%3Ewinrm%20create%20winrm%2Fconfig%2FListener%3FAddress%3D*%2BTransport%3DHTTP%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

I've raised a bug here - https://windowsserver.uservoice.com/forums/295071-management-tools/suggestions/37729852--bug-can-t-c...

 

I've installed Windows Admin Center with high availability following https://docs.microsoft.com/en-us/windows-server/manage/windows-admin-center/deploy/high-availability.

I can connect to nodes in the cluster fine through WAC, however when I try to add the cluster it says it can't find the name.

If I click on one of the nodes it gives the FQDN of the cluster, I click it and it adds it as a connection but when I try to access it, it complains that WINRM couldn't not process the operation.

I've tried it with two different clusters on our network.

 

Any ideas?

2 Replies
Highlighted

@CyclopsHelpdesk 

I've checked and the cluster IP that is on a node is showing as listening on that IP when running winrm e winrm/config/listener in PowerShell - so that doesn't seem to be the issue.

Highlighted
Deleting the listener and recreating it fixed the issue.

In PowerShell:
winrm delete winrm/config/Listener?Address=*+Transport=HTTP
winrm create winrm/config/Listener?Address=*+Transport=HTTP