RE: CEICW after loading third party certificate

Thanks, but that did not fix it.
Still
Error Code: 500 Internal Server Error. The target principal name is incorrect.

Public Name of Web Rule is "www.mydomain.com"

Issued To on Cert is "www.mydomain.com"
Organization on Cert is www.mydomain.com"

Error from BPA says:
The name of the certificate attached to the SBS Outlook via the Internet Web
Publishing Rule Web publishing rule does not match the public name. The
certificate was issued to www.mydomain.com, and the set of public names is
Not Found.

and so on - all publishing rules have the same error.

SBS listeners are listening to GoDaddy Cert above listed as www.mydomain.com
--
Regards,
Jamie


"Quack" wrote:

This may not help - however - found that disabling the "Enable Strict RPC
Compliance" served to allow me to install Net Framework 2.0 through 3.5
rollup which I had not been able to do. Could it be your certificate is okay
but the strict RPC compliance is interfering with the ability to login
remotely?
--
Quack,
I wouldn''t be asking this if I were anything but...


"thejamie" wrote:

It has been a long road but the certificate we purchased, is working
internally without errors (primarily no cross chaining). Everyone can get to
companyweb, the server report comes in clean each morning - users can VPN
without problem.

The problem is that the users still can't use OWA and the remote site.
"Error Code: 500 Internal Server Error. The target principal name is
incorrect."

The purchased certificate has an OU name "www.mydomain.com" and the CEICW
shows "www.mydomain.com" where the certificate is saved. I fear running the
CEICW again (create new certificate) as everything else is working at this
point and the last month of "excitement" is behind me.

After looking at the solutions available, it seems like running CEICW again
is the way to "fix" the OWA site so that it is available by the internet (the
whole purpose of buying a 3rd party cert is to make it available the right
way - no self-signed certs). But it already matches the site certificate
name (not the friendly name, but the OU name which is "www.mydomain.com"
replaced of course with the name of our domain.

Should I run the CEICW again and risk going under again for another month?
It really would be nice to see this purchased certificate actually work.
--
Regards,
Jamie
.

Relevant Pages

  • Re: Troubles with Microsoft Sharepoint Administration
    ... the CEICW cannot import the godaddy cert. ... The CEICW wizard is designed to generate a self-signed cert which (and if I ... allowing it to create the publishing.mydomain.com certificate. ...
    (microsoft.public.windows.server.sbs)
  • RE: Multiple Certificates On SBS
    ... The default website/directory security/view cert in IIS shows a cert ... When we run CEICW (server Management console -> Configuration ... certificate created that is located in default website. ...
    (microsoft.public.windows.server.sbs)
  • Re: Certificate Problem
    ... You don't actually have to change anything, but you may need to re-type the domain name with the same info - you should see the option to create a certificate, and the CEICW should apply it in the correct place. ... certificate for OWA that was created when OWA was setup. ... how do I remove the cert I created and reassert the expired one? ...
    (microsoft.public.windows.server.sbs)
  • Re: Error 80040300 in icwlog.txt
    ... Did you successfully finish the whole wizard? ... experience, if the CEICW wizard runs successfully, it will create all ... After you renew a new certificate, wherever you visit, from Internet or ... <500 Internal Server Error - The target principal name is incorrect. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 Pulling mail with remote POP3 client
    ... > have you re-run the CEICW and changed the cert to ... >> using the config instructions on the Intranet web site. ... >> Now I have a certificate problem as the certificate was issued by my ...
    (microsoft.public.backoffice.smallbiz)
Loading