I’ve had the same problem, with the same temporary workaround. It looks very much like the server has the buggy version of an IIS patch, as detailed here: https://support.microsoft.com/en-au/kb/2992611 or for a less technical version, here: http://odetodata.com/2014/11/microsoft-patch-ms14-066-leads-to-https-problems-with-iis-and-google-chrome/