I have "Require client certificates" enforced over SSL on IIS 6.  I
can effectively validate a client certificate without issue.
I'm having trouble forcing a client user (using IE 6) to authenticate
AGAIN afresh using a client certificate once the SSL session is

I would like to make a https call under Local System account
but I get error :
A security problem occurred.
Under another account there is no problem,

Scenario...
Have a 2003 exchange box with OWA working externally with no problems.  We
just installed a new 2007 exchange and have moved some users.  Things work
great until I try to access a mail box on the 2007 exchange server OWA.  I

When I try to copy files over 1MB to a webfolder (webdav), I get:
"an error copying some or all of the selected files "
This is just happening for one website on this IIS server (hosting about 10
others as well) and only on this one IIS server (we have a number of other

I am running Vista Ultimate 64-bit SP1 and have installed all features of IIS
7.0.  I am now trying to install Virtual Server 2005 R2 SP1 downloaded
yesterday from Microsoft (latest version 64-bit version).  When I attempt the
install, the application only shows port 80 ...

I'm running Exchange 2k3 sp2 with front end and back end servers. I
implemented the URLScan template for Exchange in KB823175 however I'm unable
to send from Outlook. When I run outlook.exe /rpcdiag everything connectos OK
but I checked the URLScan log and I get the following:

I have an IIS server that uses SSLv3 with server and client certificates from
a third-party CA.
I would like to map users to these third party certs and have my IIS
application (SharePoint) logon the account associated with the client certs.  

Trying to manage the IP restrictions in IIS 6.0 is a nightmare! The IPs are
not sortable, and aren't even sorted, so trying to go through hundreds of
IPs to delete some is a real PITA!
Is there any 3rd party util to manage IP restrictions, or some other way

A Happy New Year to all!
I built a corporate intranet site (ASP.NET, IIS 6.0, W2K3) that (until now)
was only used by domain users. The authentication mode was set to Integrated
Windows authentication, so clients could be easily identified

We have a Web site for staff use, which we maintain on a Windows 2003 Server
(SE, SP2).  The Default Web Site properties have Authentication set as
follows:  "Enable anonymous access" is unchecked; "Integrated Windows" and
"Basic" authentication are checked, and our AD Windows ...