Event ID 96 — AD CS Key Archival and Recovery - can't connect to server via dashboard or install new clients

-


moving old thread more appropriate forum: old thread http://social.technet.microsoft.com/forums/en-us/smallbusinessserver2011essentials/thread/798a1b6d-aed9-4c08-8700-cbd539faee0a/#bff23eca-7b4c-4df6-9559-24af6e479892


few weeks ago installed sbs 2011 essentials on new server, configured new domain, , added several clients domain. file sharing, remote web access, dashboard etc working. starting few days ago, cannot log onto dashboard client computer, or add new client domain, can still ping server, access shared folders, , in general see server on network. see previous thread screenshots/details. rwa works outside network, within network "license revoked" error instead of certificate name mismatch warning expected.

after digging server console, seeing lot of event 96 errors, 

i feel has godaddy ssl certificate...

microsoft info find:

event id 96 — ad cs key archival , recovery

http://technet.microsoft.com/en-us/library/cc774521(v=ws.10).aspx

====================

use cryptographic service provider supports key archival , recovery

may not possible use administrative tools resolve problems caused cryptographic providers, software component performs encryption , related tasks encryption certificate generation. however, following tasks can reveal diagnostic information assist in resolution process:

identify , test cryptographic provider.
if continue have problems , using non-microsoft provider, contact vendor troubleshooting information. 
can reset default encryption key provider, have revoke current ca exchange certificate new 1 based on new provider issued.
if continue have problems , using microsoft provider, contact microsoft customer service , support. 

cps microsoft, , "test" suggested yielded algorithm information little else. verified not have key archival set up, not sure if cause or effect... 

can tell me why seeing these errors, , if cause of connectivity issue?



Windows Server  >  Security



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