Please start by checking if WinRM is installed properly on the target: run th efollowing command on the destination to analyze and configure the WinRMservice: "winrm quickconfig. Please check the output you get
Please note that by default, no WinRM listener is configured. Even if the WinRM service is running, WS-Management protocol messages that request data can't be received nor sent, so running winrm quickconfig will help you troubleshoot if this service is running properly on the target or not. Winrm quickconfig will help you configure it on target
Use the Winrm command to locate listeners and the addresses by typing the following command at a command prompt:
winrm e winrm/config/listener
Other troubleshooting tips:
- Possible reasons could be that winrm ports are not opened.The default HTTP port is 5985. Running config checks should tell you which ports and prototocal (HTTP or HTTPs) target WinRM is configure to listen
- Check the default timeouts that can be used for any requests. The default is 60000 milliseconds. Again checking config will help you find this info. You can consider to increase it
- Are you able to scan other windows devices that are part of the same domain if yes then my guess is that your credentials are fine provided your system admins provide access at the domain level and not one server at a time.
- Are you able to scan other windows devices in the same IP Range or VLAN then my guess is that the firewall ports are open fine too provided your network administrators open ports at VLAN level and not at one target at a time.
Please like and or accept answer if it helps you.
