Test-Cluster Storage Spaces Direct WinRM Kerberos authentication failure


greetings,

i'm attempting set small test cluster s2d testing , i've been following handful of tutorials on setting without success.  one of bigger road blocks happening on in "test-cluster" portion.  when execute...

test-cluster -node myserver.mydomain.mylan -include "storage spaces direct",inventory,network,"system configuration"

... bunch of warnings storage spaces direct section.... every 1 of tests actually.  list disks, list file shares, list storage enclosures, etc. etc.  i open report file see fuss , every 1 of them i'm getting following error message:

    an error occurred while executing test.
    1 or more errors occurred.

    there error retrieving information disks node 'myserver.mydomain.mylan'.

    error code : 0x80131500;
    native error code : 1.
    winrm cannot process request. following error occurred while using kerberos authentication: cannot find computer myserver.mydomain.mylan. verify computer exists on network , name provided spelled correctly.

i'm running ps command locally server.  even so, i've enabled remote ps, set trusted hosts * (tried setting ip, server name, , fqdn too), turned off firewall, tried using enterprise admin , local server admin accounts.... still no joy.  i soldiered on past warnings , continued follow steps set cluster (it's test after all), when came adding disks storage cluster things went down hill fast. hunch it's related warnings winrm/kerberos errors.  i'm @ wits end trying decipher that's causing authentication error.  any appreciated.  

other notable information: there 1 dc , it's being hosted vm on hyper-v storage node i'm trying test against.  the hyper-v server joined domain hosted dc. there's 1 physical server parts on backorder second server make true cluster (from i've read, tests stuff gathering local disks on node should not fail because of though). dc , hv can ping , talk each other through virtual switch set "external network".

thanks in advance help,

craig


this true face-palm moment...

so, deleted , started over. clean slate install of ground up. when first loaded os, set roles , conducted test before joining domain... passed (more or less... there warnings, no winrm/kerberos authentication failures). set dc again , joined server domain... test failed. after banging head while longer, realized logged server using the local admin account, not domain admin account. after logged in domain admin account... passed.

long story short... make sure use domain account, not local account. lot of time wasted such simple fix.



Windows Server  >  High Availability (Clustering)



Comments

Popular posts from this blog

server manager error: ADAM.events.xml could not be enumerated.

Cannot access Anywhere Access using domain name?

WMI Failure: Unable to update Local Resource Group