This sounds like a recently discovered fault with a recent security update:
http://support.microsoft.com/?kbid=946627
I had this problem myself (with other sites too) and the above fixed it. In fact, the fix was included in one of the automatic updates.