the security certificate presented by this website was issued for a different website's address

The issued by name must be the same as the certificate otherwise you will get this error, I would double check the renamed DNS record points to the original domain.

djxtreme - the certificate was self assigned

georgestark - the DNS name is correct as we can access OWA through the address

Thanks

when you use OWA you will still get the Cert error but be able to continue and logon to OWA.
Outlook over RPC will not, same as mobile devices.

I know, so any ideas why this would have stopped working when the only change was the IP address?

Beavish

When you chaged the IP you must of changed a DNS record to match, has this been done correctly.

George

Hi George,

The DNS record where exactly?

Beavish

Ok, so you get the cert error, I know its along shot have restarted IIS on the Cert server.
try reinstalling the cert on the workstation.

when you view the cert are the issue to issued from the same.

Does sound weird, I would try a good old restart first.

you could try pinging the website from the workstaion and see if it comes back witht the correct IP, could be DNS

George,

Issued to and Issued by are the same, although end in .local, should this not be the full external domain name?

Yes, it should match the website you visit for OWA or in the RPC settings in Outlook

I am surprised it evere worked if the cert name is wrong, did you create a new cert afte the IP change?.

Nope, didn't create a new cert name

If you accept the name mismatch warning, does the page come up okay?


Try these for starters: Try from a new client if possible; Clear SSL State (Internet options - Content tab), temp internet files, history and cookies; 'ipconfig /flushdns' 'ipconfig /registerdns' on both client and server; export the certificate including the private key then import the resultant .pfx file then restart iis afterwards - try rebooting the server afterwards if still being a problem.

Hi Paranormastic, done this but with no success

We have created a new cert, mail.ourdomain.com and linked everything through to that but now getting the following error when trying to access OWA:

The target principal name is incorrect. (-2146893022)

This is well covered on Google but I have tried lots of suggestions already and none have worked

It seems like the server will not accept this certificate using SSL

Any help is appreciated

If you click 'yes', 'accept' to continue, or 'continue anyways', etc. (depenidng on your browser and version) does the page load okay or not?

The cert can be issued to site.domain.local or whatever as long as that is how it is being addressed by the accessing client.  If it an internal server or workstation - that's fine as the name is resolved and can be accessed directly.

If the server is accessed over the web or by another name, the client (user) could create an SSL session to a netowrk load balancer (e.g. ISA, F5/BigIP, NetScaler, etc.) that would translate the public FQDN (yoursite.domain.com) to the internal name (site.domain.local).  The NLB would then create a secondary SSL session from itself (as client) to the web server using the .local name (so you have actual end-to-end encryption over the wire, required for PCI DSS and such).

If you are doing just plain pass-through routing, then you would need to have the .com name in the cert instead of (or in addition to, using a SAN extension to the cert) the .local name - or just only access it internally.

We now have a further problem, we have created a certificate for mail.ourdomain.com and changed all relevant settings, now the OWA certificate is fine with no errors.

However RPC over HTTP will no longer work as it cannot resolve the internal server name, our last certificate was publishing.ourdomain.local so RPC over HTTP could resolve the server name because it had a record, we can put mail.ourdomain.com in the setup but it reverts back to the local servername, for which the client machines have no record of.

The only way we can currently get RPCoHTTP working is by connecting the VPN connection before setup and then disconnecting, from that point on it works fine.

Any advice?

Thanks