Windows 10: WinRM HTTPS port does not work.

Team,We have been working on this Project to ensure that the end user Laptop is able to listen to WinRM HTTPS port i.e. 5986.For the same we have generated a certificate by the hostname and applied it to the Laptop.We also made some changes to allow trusted hosts.We have disabled the firewall completely. No luck with the above steps.Can someone guide us how can we resolve this issue?Regards,Nik

:)

 

Windows Admin Center WinRM not working over VPN

Hello all, I use Windows Admin Center often to manage my server (OS: Hyper-V Server) and workstations (Windows 10 PCs), and I have WinRM configured for all of them.

However, when I switch to VPN, I can access all my workstations fine, except my server, which returns a WinRM error:

I am puzzled as to why WinRM access to the workstations works over VPN, but not the server.

In Powershell, Test-NetConnection to the server over ports 5985 and 5986 works without VPN;

however when the VPN is turned on TcpTest works on 5986 but fails for 5985.

Test-NetConnection to the workstations over ports 5985 and 5986 works with and without VPN!

Now I'm not sure what to do with this information. Any pointers in the right direction would be appreciated!

 

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?

 

A Windows 10 client accessing a SMB3 file share will in some cases use a WinRM connection (TCP/5985)

Hi Everybody,

I've made test in another Windows 10 infrastructre, i can confirm that Windows 10 requires TCP/5985 (WinRM,HTTP) additionally to the standard TCP/445 port.

I made a test against a Windows 2012 server with WinRM activated and TCP/5985 open and bingo: please find below the WinRM footage.

Either by design, either missing port requirements.

Best regards,

Laurent