when they try to access OWA internally they have the Cert issue correct? are they trying to access owa.domain.com or internal.machine.name ?
we had to make sure that our cert had both names. Google.com Learn it. Live it. Love it. On Wed, Aug 4, 2010 at 13:03, Cameron <[email protected]> wrote: > Greetings all, > We currently have a new Exchange 2010 Server running on W2K8r2. > Clients running mix of IE 7/8 > When they try and run OWA, they get an error that "The security certificat > presented by this website was issued for a different websites address". If > you click "Continue to this website (not recommended) everything works as it > should. > > It seems that the self signed certificate is not in the trusted root CA. We > do have a GoDaddy cert for external and it seems to be working fine. > > I've looked at instructions that show how to export the cert, create the > file and then explain how to import it into the Trusted Root CA, but it > fails and tells me that it can't create a PKCS #12 file. > > I'm pretty sure that there has to be an easy answer to this as the users are > *complaining" about the error. > > > As always, TIA! > Cameron > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
