Re: Owa-problem (frontend)

On Sat, 11 Nov 2006 16:44:01 -0800, jering
<jering@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

Hi!

I have a backend/frontend-topology with Exchange 2003 SP2.
I installed the frontend today, but I have som trouble getting OWA and SSL
to work.

Here is how I installed the server:
Basic OS-install of Windows Server 2003 w/SP1.
After install I set an IP-adress on the server and joined it to the domain.
I then installed Exchange 2003 and SP2.
I then set the server as a frontend and rebooted.
I then configured SSL with a certificate issued by the backend-server which
is a certificate-server.
I then opened port 80 and 443 in the Windows Firewall.
I then enabled formbased authentication.
When I try to connect to the server by https://server/exchange I get the
Formbased authentication-login screen, but when I type the password I get
"HTTP Error 403.4 - Forbidden: SSL is required to view this resource."
The same happens without the formbased authentication enabled.
The plan is to also use the frontend-server as a RPC over HTTP-proxy, so the
RPC-proxy service was installed before Exchange.

SSL was required on the backend, so I disabled it and rebooted the backend.
But still the error when connecting to the frontend is there.

I couldn`t find out what the reason was, so I then installed a new server in
the same way. But guess what....the same happens there! So it`s related to
the backend?

I could mention that both frontend-servers are installed on Virtual Server
2005 R2.

Any suggestions would be appreciated!

First off, yes, the SSL has to be disabled at the back-end. You should
also make sure that Integrated logon is enabled on the BE and that
only Basic is allowed on the FE.
Then there is the matter of the certificate. How did you "apply" for
it? Did you make it on the CA and export it, use IIS to apply directly
to an online? Use IIS to apply through Certs Manager on the FE or use
the web interface. If you didn't already, do an apply using IIS and
"send to online CA now" (I think is the term used on screen)`
There are lots of times when the cert comes without the private key
and even though the site is secured you still can't gain access to the
site.
.

Relevant Pages

  • Re: Owa-problem (frontend)
    ... I installed the frontend today, but I have som trouble getting OWA and SSL ... Basic OS-install of Windows Server 2003 w/SP1. ... After install I set an IP-adress on the server and joined it to the domain. ... SSL was required on the backend, so I disabled it and rebooted the backend. ...
    (microsoft.public.exchange.setup)
  • Re: Distributing Runtime Only
    ... Or do I need to have a database ... Generally speaking, you would split your database into a frontend (forms, ... reports, queries, macros, and modules) and backend and distribute ... edition) to each, and install it. ...
    (microsoft.public.access.devtoolkits)
  • Re: access 2007 runtime
    ... install both frontend and backend, ... backend, install just frontend. ... existing data file is never over-written. ...
    (microsoft.public.access.tablesdbdesign)
  • access 2007 runtime
    ... Is there a way to setup different install options for a split DB using Access ... install both frontend and backend, install just backend, ...
    (microsoft.public.access.tablesdbdesign)
  • Re: Trend Micro CSM Suite v2 and ISA 2004
    ... SSL is the default, and it should work. ... Run setup - install on IIS is generally the only selection available. ... Accept the client installation for the SBS (installs the Officescan ... then open the admin console. ...
    (microsoft.public.windows.server.sbs)