Re: RPC-HTTPS Certificate Question

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Goober Head (GooberHead_at_discussions.microsoft.com)
Date: 03/02/05


Date: Wed, 2 Mar 2005 11:53:04 -0800

OK :) That makes sense. I'll try that that. Is there any documentation
available you might recomend? As for the relay issue...This is a lab so I can
blow it away at any time, When I create the internal domain and name it the
same as the public domain, "domain.com", I don't get the relay problem. It
only occurs when I name the internal domain to something other then the
public FQDN.

Is it more secure to use different doman names for local and external

"Evan Dodds [MSFT]" wrote:

> For the certificate part of this, you need to install the root certificate
> to the trusted root store, not the client certificate. If your CA is set up
> properly, you should be able to view the issuing CA as you inspect the
> certificate chain (on the client certificate) and then you can choose to
> install that (root) cert to the client. If the CA is not set up properly,
> you may still have to find the root cert on the CA machine and copy the (CRT
> file, usually) over to the client machine and install manually.
>
> Once this is done, you will not have to accept the client cert each time, as
> it will have come from a (now) trusted root certificate authority.
>
> --
> Evan Dodds
> Microsoft Exchange Support
>
> ****** Disclaimer ******
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> Note: Please do not reply to this e-mail address. It is used for newsgroup
> purposes only.
>
> "Goober Head" <GooberHead@discussions.microsoft.com> wrote in message
> news:FB51443C-BD85-4617-8548-313D8BD8C7E1@microsoft.com...
> > Hello,
> > I'm trying to setup a Single server Exchange SP1 as the only system in
> > it's
> > domain.
> > It is a 2003 server, DC/GC, IIS, CA, and Exchange 2003 SP1. My hopes were
> > to
> > set this server up publicly so all employees could access it via
> > RPC-HTTPS.
> > Public= pubsystem.domain.com
> > Local= localsys.local.
> > I have ports 25 and 443 open
> >
> > OWA works through 443 but I am not able to receive mail because the
> > exchange system thinks it is being used as a relay when mail arrives
> > destined
> > for pubsystem.domain.com
> >
> > RPC through HTTPS doesn't work for me yet and I was told it was because
> > I've
> > not setup the certificate properly. The Certificate is "Issued To"
> > pubsystem.domain.com and "Issued By" localsys.local. I've installed the
> > certificate to the client via IE then using mmc, copied it to the trusted
> > root certificates. Of course my Outlook clients do not connect and
> > Outlook/diag reflects no connection of any type. If I access exchange from
> > OWA I am prompted to install the certificate every time I access exchange.
> >
> > So I need help resolving the relay issue and the certificate issue. Any
> > help
> > will be greatly appreacited. Thank you.
>
>
>



Relevant Pages

  • Re: Quick Start certificate
    ... Where do I specify what the root path is. ... Then run the client. ... Did you give your web server identity permission to ... It's done through the certificate tool that's installed ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: Require Certificates
    ... Make sure the root CA is trusted on both client and on IIS server. ... > Empty certificate selection list is usually a sign of missing private key. ... >> certified the web site and imported the Root CA cert. ...
    (microsoft.public.win2000.security)
  • RE: SEC_E_UNTRUSTED_ROOT
    ... As I indicated I had downloaded the root CA ... After reviewing the certificate information in the registry I decided to use ... environment on my client machine. ... To test my application I have set up a Windows 2000 server ...
    (microsoft.public.platformsdk.security)
  • Re: Checkpoint smart defance as IPS
    ... *any* SSL/TLS communication without tampering anything on the client ... website a client visits on-the-fly. ... don't have private key for the certificate on that website. ...
    (Security-Basics)
  • Re: Checkpoint smart defance as IPS
    ... *any* SSL/TLS communication without tampering anything on the client ... website a client visits on-the-fly. ... don't have private key for the certificate on that website. ...
    (Security-Basics)