Changing the IPHTTPS tunnel certificate in DirectAccess
Yet another day of troubleshooting DirectAccess, this time it was about a broken IPHTTPS tunnel. During the troubleshooting we recognized that the client is not able to establish a connection the the IPHTTPS url https://da.domain.com/IPHTTPS, using a network sniffer we could very clear see the server sending a reset packet after the Client Hello message. This indicates that the SSL server is not able to continue communicating using SSL. Knowing that there was a certificate change just a few days before this error occurred we found that the old certificate was still used for the SSL binding at the DA server even though the configuration was reapplied using the DA management console after the certificate change.
When changing the certificate used for the IPHTTPS tunnel it is very important to clear the old SSL certificate binding before adding the new one.
If you configured your DirectAccess using the DA management console follow the steps below to change the IPHTTPS certificate:
· Run the command: netsh http show sslcert
This will show the current sslcert binding with details about ip, port and the certificate
· Delete the old bindning using the command: netsh http del sslcert
· Using the DA management console, select the new IPHTTPS certificate, save an apply the new configuration
If you configured your DirectAccess using scripts or netsh commands to define all setting follow the steps below to change the IPHTTPS certificate:
· Run the command: netsh http show sslcert
This will show the current sslcert binding with details about ip, port and the certificate
· Delete the old bindning using the command: netsh http del sslcert
· Add the new sslcert binding using the command: netsh http add sslcert
/Hasain
