WAC stopped connecting to machines via WinRM over the past week

[aggietallboy]

Last week I installed the 2211 update for WAC. I tested connectivity to ~5 of our machines, and was pretty satisfied. Now I can connect to nothing.

400 - PSRemotingTransportException: Connecting to remote server myserver.fqdn failed with the following error message : WinRM cannot complete the operation. Verify that the specified computer name is valid, that the computer is accessible over the network, and that a firewall exception for the WinRM service is enabled and allows access from this computer. By default, the WinRM firewall exception for public profiles limits access to remote computers within the same local subnet. For more information, see the about_Remote_Troubleshooting Help topic. Stack trace: at System.Management.Automation.Runspaces.AsyncResult.EndInvoke() at System.Management.Automation.Runspaces.Internal.RunspacePoolInternal.EndOpen(IAsyncResult asyncResult) at System.Management.Automation.RemoteRunspace.Open() at Microsoft.ManagementExperience.PowerShell.PowerShellOperations.<>c__DisplayClass9_0.b0() at System.Threading.Tasks.Task`1.InnerInvoke() at System.Threading.Tasks.Task.Execute() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.ManagementExperience.PowerShell.PowerShellApi.d9.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.ManagementExperience.FrontEnd.Controllers.FeatureController.d89.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Threading.Tasks.TaskHelpersExtensions.d3`1.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Web.Http.Controllers.ApiControllerActionInvoker.d0.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.ManagementExperience.FrontEnd.Handlers.ImpersonationActionInvoker.d1.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Web.Http.Controllers.ActionFilterResult.d2.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Web.Http.Dispatcher.HttpControllerDispatcher.d1.MoveNext()

But from powershell on the WAC gateway machine:

PS C:\Windows\system32> test-wsman myserver.fqdn

wsmid : http://schemas.dmtf.org/wbem/wsman/identity/1/wsmanidentity.xsd ProtocolVersion : http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd ProductVendor : Microsoft Corporation ProductVersion : OS: 0.0.0 SP: 0.0 Stack: 3.0

A-OK right?

Same behavior with windows login and with "manage as" Same behavior from local machine where WAC is installed and from remote machine calling WAC.

ONLY machine I seem to be able to connect to right now is the WAC machine itself¿and even that is only when run locally.

I've reinstalled WAC, to no avail

Also confirmed connectivity to targeţmyserver.fqdn by adding to Server Manager -- everything populated as expected.

Server OS - Server 2022 Datacenter 20348.1366 Hyper-V VM 4 vCPU (Xeon E5-2667 v4) 16 GB RAM

Windows Admin Center 2211

MS Edge on local WAC console server Chrome on remote connection

Tested regular and incognito

[aggietallboy]

I can connect to the WAC gateway machine from other machines

[aggietallboy]

DOH It was me... i flagged use SSL for WinRM. Undid the registry setting and lo and behold and we can connect again.

[aggietallboy]

https://techcommunity.microsoft.com/t5/windows-admin-center/windows-admin-center-revert-quot-use-winrm-over-https-only-quot/m-p/1585108