Re: HTTP over RPC problem
From: Patrik (Patrik_at_discussions.microsoft.com)
Date: 11/22/04
- Next message: Mark Arnold [MVP]: "Re: Use of Alternate Recovery Forest"
- Previous message: Mark Arnold [MVP]: "Re: Exchange 2003 Web interface and tailoring it..."
- In reply to: Mark Arnold [MVP]: "Re: HTTP over RPC problem"
- Next in thread: Mark Arnold [MVP]: "Re: HTTP over RPC problem"
- Reply: Mark Arnold [MVP]: "Re: HTTP over RPC problem"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 22 Nov 2004 12:19:03 -0800
I'll have to check that when I go to work tomorrow, but I accessed OWA to
double check and the certificate says server.domain.com or to be more exact,
it says webmail.domain.com which is not the name of the server but the URL to
OWA.
One question, is the certificate used for the Outlook client as well as OWA?
I thought it was for OWA only, which works just fine. I do get a warning
every time I go to the OWA logon page stating
"The security certificate was issued by a company you have not chosen to
trust..."
If i view the certificate I can't view the issuer if I'm not running from a
computer that is member of the domain and connected to the LAN, probably
because the issuer is dc.domain.local which cannot be resolved on the
internet.
About half of the users running Outlook from remote locations work on
computers that is not members of the domain if that is of importance.
"Mark Arnold [MVP]" wrote:
> On Mon, 22 Nov 2004 11:35:02 -0800, Patrik
> <Patrik@discussions.microsoft.com> wrote:
>
> >Yes, I'm using SSL with an internal certificate but the certificate is saying
> >server.domain.com, not server.domain.local. I have had users that used a
> >hosts file and that worked fine in most cases, but some users experienced
> >some problems when they connected via VPN. I guess I'll have to go with the
> >hosts file and try to solve any errors that may occur.
> >
> >Many thanks,
> >Patrik
> >
> How did you manage to get the internal certificate to say
> "server.domain.com" rather than "server.domain.local"?
> If that had happened then the cert name would have matched the FQDN
> used and you wouldn't have had the problem in the first place.
> Confused...
>
>
- Next message: Mark Arnold [MVP]: "Re: Use of Alternate Recovery Forest"
- Previous message: Mark Arnold [MVP]: "Re: Exchange 2003 Web interface and tailoring it..."
- In reply to: Mark Arnold [MVP]: "Re: HTTP over RPC problem"
- Next in thread: Mark Arnold [MVP]: "Re: HTTP over RPC problem"
- Reply: Mark Arnold [MVP]: "Re: HTTP over RPC problem"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|