Windows Server / DNS, DHCP & Server Networking
Inspect WinRM listener configuration when remote administration fails
A server may have a running WinRM service without a listener matching the intended interface or transport.
Environment and inputs: Windows Server 2022 / 2025 baseline · Windows PowerShell with the specified role or RSAT modules; native utilities are identified in the text. Use delegated administration and elevation only where required.
Start with this check
Confirm the host, shell and access role. Replace sample names, paths, domains and interfaces with approved targets. These are diagnostic commands; assess policy and workload impact before making changes.
winrm enumerate winrm/config/listenerRead the result
Run in an authorized Windows terminal. The output shows configured listeners, addresses and ports; remote firewall and identity paths still need separate checks.
Resolve and verify
Compare the listener with the approved HTTP or HTTPS management design, then test from the intended administration host. Correct the narrow configuration or certificate issue.
Before changing production
Do not set broad TrustedHosts values or disable authentication protections as a generic fix.