Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

After doing some fairly inconsequential set up of a new Windows 2008 server instance it will cease responding to any connection attempts after a reboot. RDP, HTTP, HTTPS, you name it. I am unsure if this is because the installation has become corrupt or if something in Windows 2008 is triggering security measures and simply blocking all inbound connections.

share|improve this question
up vote 2 down vote accepted

A user on the Amazon forum's led me to a solution. The problem will occur after binding an SSL cert to a website in IIS that was not issued from a recognized CA. I'm not sure if this would be classified as a bug or by design but it's confusing either way. To resolve the issue you must verify the existence of the issuing CA's certificate in the Trusted Root Certificate Authorities store. You can do this with the following steps:

  1. Click Start
  2. Type 'mmc' in the search and hit enter
  3. Click file->add remove snap in
  4. Locate the Certificates snap in and click Add
  5. Select the Computer Account
  6. Click Ok
  7. Expand the Certificates snap in
  8. Locate the Trusted Root Certificate Authorities store

If the issuing CA of your SSL cert does not exist you must import it into the store. You can do this by retrieving a cer file for the issuing CA, and importing it by right clicking and selecting All Tasks->Import... and following the steps in the wizard.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.