HYPER-V Manager cannot connect locally after 24+ hours

-

2 * server 2008 hyper-v cluster sp2 (non-r2).
both servers domain controllers _only_ cluster domain (hv01.cluster-domain.local , hv02.cluster-domain.local) keep network separated normal network.
cluster works fine, 8 virtual machines, wandering node node, fine.

hyper-v manager cannot connect machines after while, after day, on 1 machine says "cannot connect", on other machine says "connecting" never connects. can still switch machines node node, , can still shutdown , reboot machines cluster manager.

putting resources on node one, reboot node two: hyper-v manager works again on node two.
after putting resources on node 2 , reboot node one, hyper-v manager works on 1 too.

have no eventlog entries showing error message, stunned reason hyper-v manager unable connect after day.

hi.

have checked hyper-v-vmms error log ?

it`s located under applications , services logs\microsoft\windows\hyper-v-vmms

cant connect vms remotely ?

check hyper-v hosts listening on port 2179, , can connect through port.

 

kristian


Windows Server  >  High Availability (Clustering)



Comments

Post a Comment

Popular posts from this blog

WIMMount (HSM) causing cluster storage to go redirected (2012r2 DC)

-
looking options resolve error , prevent in future. thanks help. hardware: 2 node dell hv cluster running2012r2 dc 8 nic/ea in multiplex mode 4x hyper-v 4x hosts storage: 2x synology nas, accessed through iscsi hosts , cluster relevant logs: log name:      microsoft-windows-failoverclustering/diagnostic source:        microsoft-windows-failoverclustering date:          event id:      2050 task category: none level:         warning keywords:       user:          system computer:      l description: [dcm] filter wimmount found @ unsafe altitude 180700 log name:      system source:        microsoft-windows-failoverclustering ...
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

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