We run IIS4 on NT Server 4 SP5-128. Recently when binding PKI certificates to individual sites, I experienced an odd phenomenon I hope someone can shed some light on. After binding the individual certificates to the sites (4 of them sequentially)I Committed the Changes, and saved the MMC 1.1 console file to disk. At that point the bindings dialogue accurately reflected the individual certificate-socket bindings. 10 minutes later, I had to revisit the MMC. When I opened the Key Manager module All the certificate socket bindings had reverted to a previous one-certificate- to-many-sockets configuration, and none of my previous changes were in evidence. Attempts to reimport the key files were repeatedly unsuccessful. Nevertheless, if accessing any of the sites in question via https, the client browser acts as if the proper certificate is present, and does not give any indication otherwise-“Cerificate matches page you are trying to view”
Does anyone have any suggestions on recovering the usability of those key pairs? I’d like to avoid having to repeat the generation, application, and installation steps I’ve done thus far, if at all possible?