WinRM Negotiate authentication error when connecting to HyperV Server 2016 on workgroup

-

hi,

i’m trying configure hyperv server 2016 on workgroup via server manager on win10 pro machine , receiving ‘winrm negotiate authentication error’ in respect hyperv server

configuration

  • local machine windows 10 pro (updates applied) server manager build date 9<sup>th</sup> oct 2016.
  • remote machine hyperv server 2016 (updates applied)
  • both machines on same workgroup, have identical user/password accounts. tcpip configured same subnet, gateway etc each static ip
  • both machines connected same ethernet switch

i’ve done lots of research seem have missed winrm error persists. these steps i’ve applied far of have run successfully;

  • applied firewall rules on hyperv server

           netsh advfirewall firewall set rule group="windows management instrumentation (wmi)" new enable=yes

           netsh advfirewall firewall set rule group="remote event log management" new enable=yes

  • run wsman command on local machine

             set-item wsman:\localhost\client\trustedhosts hvserver -concatenate -force

  • added hyperv server hosts, lmhosts.sam files on windows 10 machine
  • run get-service winrmon hyperv sever , confirmed winrm service running
  • run winrm quickconfig on hyperv server

what can is;

-          ping hyperv server successfully

-          from server manager can following on hyperv server;

  • open computer management
  • run remote desktop session

other don’t other functionality within server manager.

what missing?

cheers,

an update...

i reran wsman command server.workgroup param rather server. i.e.

set-item wsman:\localhost\client\trustedhosts server.workgroup -concatenate -force

problem solved



Windows Server  >  Server Manager



Comments

Post a Comment

Popular posts from this blog

Azure MFA with Azure AD and RDS

-
i have setup following lab in azure , need help. a server (domain controller) , remote desktop services. and server multi factor authentication server. i have setup following one http://www.rdsgurus.com/uncategorized/step-by-step-using-windows-server-2012-r2-rd-gateway-with-azure-multifactor-authentication/ and when im connecting got following error. the user "domain\username", on client computer "xxx.xxx.xxx.xxx", did not meet connection authorization policy requirements , therefore not authorized access rd gateway server. authentication method used was: "ntlm" , connection protocol used: "rpc-http". following error occurred: "23003". also on security log i've got following authentication details: connection request policy name: ts gateway authorization policy network policy name: - authentication provider: radius proxy authentication server: test.test.local authenticati...
Read more

Failed to delete the test record dcdiag-test-record in zone test.com

-
ps c:\users\administrator.test> dcdiag /test:dns directory server diagnosis performing initial setup:    trying find home server...    home server = dc02    * identified ad forest.    done gathering initial info. doing initial required tests    testing server: default-first-site-name\dc02       starting test: connectivity          ......................... dc02 passed test connectivity doing primary tests    testing server: default-first-site-name\dc02       starting test: dns          dns tests running , not hung. please wait few minutes...          ......................... dc02 passed test dns    running partition tests on : forestdnszones    running partition tests on : domaindnszones    running partition tests on : schema ...
Read more

Failed to setup initiator portal. Error status is given in the dump data.

-
hi team, server configured boot san  after booting  facing issue windows server 2008 r2 system logs continuously generating iscsi port error event id 5 failed setup initiator portal. error status given in dump data. eventdata \device\raidport1 000004000100000000000000050000c0000000000000000000000000000000000000000000000000070200c0 binary data: in words 0000: 00040000 00000001 00000000 c0000005 0008: 00000000 00000000 00000000 00000000 0010: 00000000 00000000 c0000207 in bytes 0000: 00 00 04 00 01 00 00 00 ........ 0008: 00 00 00 00 05 00 00 c0 .......À 0010: 00 00 00 00 00 00 00 00 ........ 0018: 00 00 00 00 00 00 00 00 ........ 0020: 00 00 00 00 00 00 00 00 ........ 0028: 07 02 00 c0 ...À hi, please read through article below troubleshoot issue: error event id 5 logged in system log on computer uses iscsi software initiator connect iscsi target device http://suppo...
Read more