Wednesday 23 September 2015

Skype4B / IIS 8 not presenting new certificate in browser.

After replacing a couple of old, soon to expire, default certificates on the frontend pool, I discovered that the old certificate was still being presented to the client.

Checking the IIS manager binding for the website, I saw the correctly assigned new certificate.

Running this command:
netsh http show sslcert
Showed that some of the ippools still having the thumbprint of the old certificate, so going back into bindings for the website. I changed the IP address assignment from Any unused to the IP address of the server, resetting the IIS (iisreset.exe) and changing the IP address assignment back to Any unused.

Ran the command again and this time the correct thumbprint was shown for all the ippools.

Test showed the correct certificate now being presented to clients.

Thursday 10 September 2015

Skype4B web plugin cannot establish media to meeting

Over some time I have been troubleshooting a problem where a customer cannot connect to Skype4B Online meetings using the Skype Web plugin. Connecting media failed.


Research showed that connecting to a Lync 2013 online meeting using the Lync Web App plugin worked fine, but the connecting to the same meeting using the Skype4B Web App plugin didn't work.


The customer has a Websense proxy server farm set up using SSL inspection, so we tried to remove SSL inspection as this is unsupported (according to Microsoft PSS - not documented).


Tracing the proxy server, we saw the Skype4B not authenticating towards the Websense proxy. Websense requesting Kerberos, NTLM and Basic authentication. Removing authentication for the meeting.domain did not change anything.


Still no resolution, but it does look like a bug in the Skype4B Web App plugin.