Hyper-V Manager unable to connect to my server
Solved
Fixir
Posted messages
16
Status
Membre
-
Fixir Posted messages 16 Status Membre -
Fixir Posted messages 16 Status Membre -
Lexicon:
my machine = the PC running Win10 Pro from which I connect to the server
my server = the server running on Microsoft Hyper-V Server 2016 named ***
Hello,
I'm going to try to explain myself as best as I can as I'm a beginner in this field..
So here is my problem:
I installed Windows Hyper-V Server 2016 following Microsoft's tutorial on my server (the server is at my home).
The installation goes smoothly, but when I try to connect for the first time to my server from another computer with the Hyper-V Manager in Windows 10 (Pro), I receive an error (which I did not note as I corrected it) indicating that I needed to use winrm quickconfig.
As soon as I heard that, I executed this command.
I then tried to connect to the server again. The server did not take it well, and I received the message:
Having executed the aforementioned command on the server (winrm help config), the console returned several commands that are supposed to help me (I suppose).
I decided to ignore them since the descriptions did not seem to correspond to my problem (though I'm not sure if I fully understood the issue...).
I then searched for solutions on forums. One solution seemed to help (I think):
The proposed solution was to add the server to the TrustedHosts of my machine (from what I understood):
Start-Service WinRM
winrm set winrm/config/client '@{TrustedHosts='***'}' /*returns a sort of "report" of WinRM settings*/
Stop-Service WinRM
Since then, I get a new error but not every time (strange ..), indicating an error code 0x8009030e. The error details indicate:
I have tried to find solutions to this problem, but I really can't see any. Also, there's the Negotiate authentication mode that I've never configured and I don't know where it might come from, unless it's the default mode...
Thank you for reading
and thank you in advance for your help
Fixir
my machine = the PC running Win10 Pro from which I connect to the server
my server = the server running on Microsoft Hyper-V Server 2016 named ***
Hello,
I'm going to try to explain myself as best as I can as I'm a beginner in this field..
So here is my problem:
I installed Windows Hyper-V Server 2016 following Microsoft's tutorial on my server (the server is at my home).
The installation goes smoothly, but when I try to connect for the first time to my server from another computer with the Hyper-V Manager in Windows 10 (Pro), I receive an error (which I did not note as I corrected it) indicating that I needed to use winrm quickconfig.
As soon as I heard that, I executed this command.
I then tried to connect to the server again. The server did not take it well, and I received the message:
An error occurred while attempting to connect to the server "***". Verify that the virtual machine management service is running and that you are authorized to connect to the server.
Operation failed on computer ***: The WinRM client cannot process the request. If the authentication scheme is not Kerberos, or if the computer is not a member of a domain, HTTPS transport must be used, or the destination computer must be added to the TrustedHosts configuration setting. Note that computers in the TrustedHosts list may not be authenticated. For more information, run the following command: winrm help config
Having executed the aforementioned command on the server (winrm help config), the console returned several commands that are supposed to help me (I suppose).
I decided to ignore them since the descriptions did not seem to correspond to my problem (though I'm not sure if I fully understood the issue...).
I then searched for solutions on forums. One solution seemed to help (I think):
The proposed solution was to add the server to the TrustedHosts of my machine (from what I understood):
- In an admin PowerShell*
Start-Service WinRM
winrm set winrm/config/client '@{TrustedHosts='***'}' /*returns a sort of "report" of WinRM settings*/
Stop-Service WinRM
- End*
Since then, I get a new error but not every time (strange ..), indicating an error code 0x8009030e. The error details indicate:
An error occurred while attempting to connect to the server "***". Verify that the virtual machine management service is running and that you are authorized to connect to the server.
Operation failed on computer ***: The WinRM client cannot process the request. The following error occurred with code 0x8009030e when using Negotiate authentication: A specified logon session does not exist. It may already have been terminated.
I have tried to find solutions to this problem, but I really can't see any. Also, there's the Negotiate authentication mode that I've never configured and I don't know where it might come from, unless it's the default mode...
Thank you for reading
and thank you in advance for your help
Fixir
1 réponse
Hello,
The account used for your authentication indeed belongs to the "hyperv administrators" group on the server...
Ideally, having a domain would have been better. It would be easier to avoid the authentication issues you are currently facing.
Failing that, the server and the user workstation do belong to the same workgroup...
Best regards.
--
Ignorance and folly have their pleasures just as the spirit and knowledge do.
The account used for your authentication indeed belongs to the "hyperv administrators" group on the server...
Ideally, having a domain would have been better. It would be easier to avoid the authentication issues you are currently facing.
Failing that, the server and the user workstation do belong to the same workgroup...
Best regards.
--
Ignorance and folly have their pleasures just as the spirit and knowledge do.
However, when I use this function, it tells me that the username is not valid (regardless of what I enter).
Also, for the moment, there is only one account on the server, and it is the one created during installation (Administrator).
Otherwise, yes, the server and the workstation are indeed in the same workgroup since both show WORKGROUP in the workgroup section.
Moreover, both machines are on the same LAN; they should have no problem seeing each other (in fact, I can ping the server from the workstation).
Thank you for your response.
Nevertheless, if the administrator account does not belong to the Hyper-V administrator group, you will not be able to administer it remotely.
Then, to authenticate remotely, you need to enter the username in the form servername\administrator (replace servername with the name of your Hyper-V server).