Home

[Bug] Can't connect to cluster or node running WAC

%3CLINGO-SUB%20id%3D%22lingo-sub-658194%22%20slang%3D%22en-US%22%3E%5BBug%5D%20Can't%20connect%20to%20cluster%20or%20node%20running%20WAC%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-658194%22%20slang%3D%22en-US%22%3E%3CP%3EOur%20environment%20is%20a%20Hyper-V%20hyper-converged%20S2D%20cluster%20running%20Windows%20Server%202016%20Datacenter%20edition.%3CBR%20%2F%3EWAC%20has%20been%20installed%20as%20a%20high%20availability%20deployment%20option%20called%20wac.%3C%2FP%3E%3CP%3EWAC%20is%20currently%20running%20on%20node%201%20in%20the%20cluster.%3CBR%20%2F%3EWhen%20it%20is%20on%20node%201%2C%20connecting%20to%20node%201%20in%20WAC%20is%20really%20slow%20and%20connecting%20to%20node%202%20in%20WAC%20is%20really%20fast.%3C%2FP%3E%3CP%3EIf%20I%20failover%20WAC%20to%20node%202%2C%20then%20connecting%20to%20node%201%20in%20WAC%20is%20really%20fast%20and%20connecting%20to%20node%202%20is%20really%20slow.%3C%2FP%3E%3CP%3EIf%20I%20try%20and%20add%20the%20cluster%20by%20it's%20FQDN%20it%20says%20it%20cannot%20verify%20it's%20network.%20If%20I%20click%20the%20blue%20hyper-link%20to%20the%20cluster%20from%20one%20of%20the%20nodes%20via%20their%20WAC%20page%20it%20adds%20the%20cluster%20but%20it%20fails%20to%20load.%20It%20prompts%20for%20credentials%2C%20using%20my%20windows%20credentials%20or%20supplying%20alternative%20credentials%20does%20not%20work.%20It%20says%20that%20the%20process%20could%20not%20be%20completed.%3CBR%20%2F%3EKerberos%20delegation%20has%20been%20done%20as%20documented%20by%20MSFT%20for%20the%20SSO%20to%20work.%3CBR%20%2F%3EWinrm%20is%20enabled%20and%20listening%20on%20HTTP%20on%20all%20IPs%20on%20all%20nodes.%3C%2FP%3E%3CP%3EWe%20have%20another%20cluster%20-%20cluster2%20that%20is%20also%20Hyper-V%20hyper-converged%20running%20Windows%20Server%202016%20Data%20edition.%3CBR%20%2F%3EIf%20I%20try%20and%20access%20that%20cluster%20or%20it's%20nodes%20from%20the%20same%20WAC%20install%20it%20works%20absolutely%20fine.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-658194%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EBUG%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Ecluster%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
CyclopsHelpdesk
Occasional Contributor

Our environment is a Hyper-V hyper-converged S2D cluster running Windows Server 2016 Datacenter edition.
WAC has been installed as a high availability deployment option called wac.

WAC is currently running on node 1 in the cluster.
When it is on node 1, connecting to node 1 in WAC is really slow and connecting to node 2 in WAC is really fast.

If I failover WAC to node 2, then connecting to node 1 in WAC is really fast and connecting to node 2 is really slow.

If I try and add the cluster by it's FQDN it says it cannot verify it's network. If I click the blue hyper-link to the cluster from one of the nodes via their WAC page it adds the cluster but it fails to load. It prompts for credentials, using my windows credentials or supplying alternative credentials does not work. It says that the process could not be completed.
Kerberos delegation has been done as documented by MSFT for the SSO to work.
Winrm is enabled and listening on HTTP on all IPs on all nodes.

We have another cluster - cluster2 that is also Hyper-V hyper-converged running Windows Server 2016 Data edition.
If I try and access that cluster or it's nodes from the same WAC install it works absolutely fine.