My server has got IIS7 with two sites Site1 and Site2. I have them each on their own distinct Ipv4 address, each on their own separate certificate, and both are on port 443. The issue I am experiencing is that if I take Site1 offline, the server is still responding to ssl on that site's address and...

I have a server that has Windows Server 2008 standard with Exchange 2007 installed. I installed the RPCProxy feature in order to use Outlook Anywhere. Looking at the RPC web's SSL settings they were set to Do not require SSL and Accept Client Certificates. I was having a problem with my outlook anywhere...

I have NLB configured, but i want to perform node level monitoring and in that process, i have added dedicated IP to SSL identities in website along with shared IP, i am able to browse website with dedicated IP on the box without any issues. But when i try to open website using dedicated box from my...

One of the businesses for whom I consult called me up to have me change the settings on their IIS 6.0/Exchange 2003 server so their main accountant/IT support person could get Outlook Mobile Access on his new Palm Pre. Apparently, the Pre will choke when it encounters a SSL certificate that is not linked...

When POSTing content of bigger size (more than 500 KB let's say) "413 - Request Entity Too Large" is returned by IIS7. Solving the error with increasing the value of maxAllowedContentLength works for http. When issuing an SSL POST request on the same resource, modifying maxAllowedContentLength...

I built some tools that you might find handy: Web Based Tool to see if SSLv2 is enabled Windows GUI to disable SSLv2, and other weak ciphers and protocols

I internet web applications, on a dedicated Server 2008 with IIS 7, which need to send out e-mails. I have external e-mail hosting and that SMTP server requires login/password authentication, SSL and uses port 465. So far I haven't been able to get our apps to send out mail. They will send to an...

I installed a certificate from Comodo and it was working fine for one of my websites. Suddenly, the website stopped responding whenever accessed in secure mode (https). I checked the other websites sharing the server and did not find the port 443 associated to any other site. When checked with netstat...

Thanks Anil: Got it sorted. The trick was to reissue the certificate request (with the same values), and on re-import make sure that the "Friendly Name" matches the "Common Name" on the certificate (e.g., *.domain.com ). It looks like IIS 7 uses the Friendly Name to determine if you...

Thanks for that, but the certificate was issued to *.domain.com (and that is the Common Name), but when I imported the certificate I used domain.com as the Friendly Name. I was not aware that IIS7 cared about the Friendly Name. I believed that the only name that mattered was the Common Name (which is...