Windows 10: WinRM error "The device is not ready"

Hi,I'm trying to connect to a windows node windows server 2022 via WINRM using ansible and I'm getting "The device not ready error". I have researched a lot about this and did not find much promising information about this. Are there any insights that I can get to resolve this? Sahan.

:)

 

Unable to configure WinRM on domain user

Hi everyone,

I'm unable to configure WinRM on a domain computer. I have a simple domain with

1) Windows server 2012

2) A client running Windows 7

If I try to run WinRM on the local Administrator, everything works fine, but if I switch to a domain user, than problems occured.

For example, if i run winrm quickconfig in powershell as the domain Administrator, then I get:

WinRM already is set up to receive requests on this machine.

WSManFault

Message = WinRM cannot process the request. The following error occured while using Negotiate authentication: An unknown security error occurred.

Possible causes are:

-The user name or password specified are invalid.

-Kerberos is used when no authentication method and no user name are specified.

-Kerberos accepts domain user names, but not local user names.

-The Service Principal Name (SPN) for the remote computer name and port does not exist.

-The client and remote computers are in different domains and there is no trust between the two domains.

After checking for the above issues, try the following:

-Check the Event Viewer for events related to authentication.

-Change the authentication method; add the destination computer to the WinRM TrustedHosts configuration setting or use

HTTPS transport.

Note that computers in the TrustedHosts list might not be authenticated.

-For more information about WinRM configuration, run the following command: winrm help config.

Error number: -2144108387 0x8033809D

An unknown security error occurred.

When i run it as local admin, everything goes well.

So, what am I missing?

 

winrm will not enable

We are not able to enable/add windows features through the gui. We get an error each time that says the issue is due to winrm now being to start successfully,

 

Error: No work available to process

Hmm. Either it's put out errors and WCG is limiting the work units available, or the project list may not be set to supply other WU when one runs out. (if the problem lies here and not on your end)

On the options to your left, if you go into Results Status, select the computer from Device Name and then look through results see if either they were returned late, errors or any other kind of issue that would stop the servers supplying WU from that perspective.

If there are no errors then it's maybe down to your project list. So selecting Device Manager from the left menu and then clicking on the profile assigned to that computer and make sure that it's assigned to receive WU for other projects if they run out.

At least those steps will rule out problems from the WCG end.