I have 4 Web servers in an NLB cluster
I had to rebuild one of the servers from Scratch and reinstall the SSL
certificate
When I add the rebuilt server back to the cluster some of the end users get
an error when they click on a secure link " The security certificate has
expired or is not yet valid" and the name on the security cert is invaild or
does not match the name of the site".

when I check the certificate in IIS on the rebuilt server it looks to be
valid.
When I compare it to the other web servers certs it looks to be exactly the
same including the www name and the expirey dates etc.

Any idea what could be causing this?

regards,

SUMMARY/OVERVIEW:
From the C# back-end, we are instantiating an Out-of-proc COM object. That
COM object constructs an active X control to process some requests in it
before returning data back to the C# back-end. We've modified the active X
control to not put up any modal dialogs (hoping this would allow us to use
it). And the processing the active X control does do does not require any
human interaction as everything is specified through parameter passing.

CODE THAT FAILS:
In the Out of Proc COM object, we have code like the following to construct
the active X control. This code is executed when the C# back-end
instantiates us and passes us a command to process.

RECT rect = { 0, 0, 0, 0 };
HWND hWndParent = NULL;

// create the parent window
pwndParent = new CAxWindow2;

My website is hosted on a W2K3 server.
It is accessible from any public IP address (internet).
However, it is not accessible from any private IP address (internal
network).

The configuration is as follows:

Client 192.168.0.101
Server 192.168.0.11

My network is connected to the internet via a dedicated T1 link.
My hardware firewall routes port 80 traffic from internet to the IIS Server
at 192.168.0.11.
My site works fine from any internet IP address.

However, my site can not be accessed from any computer on the internal
network.
HTTP://192.168.0.11 or http://mycompanywebsite.com fails.

http://127.0.0.1 also fails on the IIS server box.

The IIS log indicates that the request was received but it logs 404 0 2
error.
(Denied dud to LOCKDOWN policy)

I have no IP address restrictions on this website.

I have IIS 5 on Windows XP Pro. I need to setup a website using certificate
Mapping.
The site is SSL enabled using a server certificated acquired from our
trusted CA.
The site is set up to "request client certificates"; i've also enabled
"client certificate mapping" and added a one to one mapping with my user
account associated to a client certificate obtained from our CA.
It all works on my computer.
If another employee (with his client certificate, but not mapped) try to
navigate the site, he can access with his certificate even if he is not
mapped. Why?
I need to enable only mapped users.