Directaccess - IPHTTPS error 0x80190194, Server 2012R2 / Win 8.1

Question

I'm trying to setup directaccess for our network.  I already have a server in our edge network with the remote access role installed for the Web Application Proxy service, so I added the DirectAccess role service to that.  According to the documentation,
if both are a single server implementation it is supported to run both of those on the same server. 
I configured DirectAccess, and added a win8.1 client to the DA security group to test it.  I confirmed that on the internal network, the client is able to connect to the NLS and DA shows that it is connected to the local network.  However, when
on an outside network, DA just says it's trying to connect, and never does.  I ran the log collection tool from the DA connection settings and found that the IPHTTPS connection shows an error code 0x80190194.  
I've searched for info on this, but so far I'm not finding anything that seems to fit my situation.  The responses to others with this error seem to point to a certificate issue.  In my case, I'm using a wildcard certificate for our public domain
name.  The cert is signed by a major public CA, so there shouldn't be any trust issues.  The external DNS name that DA should connect to is RAS.domain.com and the certificate is for *.domain.com 
Any suggestions on what the problem could be, or what to look at next for troubleshooting the issue, would be appreciated. 
Thanks!

Answer 1

Thank you for the reply.  I ran netsh http show ssl, and the first entry returned is:
SSL Certificate bindings:
    IP:port                      : 0.0.0.0:443
    Certificate Hash             : 1414baa1409b2c8ffd8c2d549f460db4bcf8130f
    Application ID               : {f955c070-e044-456c-ac00-e9e4275b3f04}
    Certificate Store Name       : MY
    Verify Client Certificate Revocation : Enabled
    Verify Revocation Using Cached Client Certificate Only : Disabled
    Usage Check                  : Enabled
    Revocation Freshness Time    : 0
    URL Retrieval Timeout        : 0
    Ctl Identifier               : (null)
    Ctl Store Name               : (null)
    DS Mapper Usage              : Disabled
    Negotiate Client Certificate : Disabled
That is followed by several entries for addresses related to our Lync and ADFS servers, published through Web Application Proxy.  All of those have the same certificate hash listed, which makes sense since I am using the same wildcard certificate for
WAP and DA.  
I did find a post or two indicating that the DS Mapper Usage may need to be set to enabled, so I tried that last week but it didn't seem to make any difference.