Re: Owa-problem (frontend)

I found the cause...Require SSL was set on the Exchange virtual folder on the
BE. I was sure I checked this, but doublechecking is obviously the thing...

"jering" wrote:

Hi!

Now Integrated and Basic is enabled on the BE, and only Basic on the FE.
I used the webinterface on the certsrv and pasted the request from the fe to
get the certificate, but today I removed that certificate and genereated a
new one with the method you mentioned ("send to online CA now").
I made an iisreset on both BE and FE, but still, the same thing happen.
I`m wondering if this could be related to the RPC-proxy I installed and
enabled, so I`m a bit tempted to install another FE without SSL and
RPC-proxy, just to see that it works that way...

"Mark Arnold [MVP]" wrote:

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: REDIR.ASP file in use - access denied when installing Exchange 2003 SP1
    ... To resolve the problem i gave the 'Server Operators' group Full Control ... As soon as this was done the install worked fine. ... > Installation Instructions for Service Pack 1 for Windows Small Business ... What's the exact error message when you are installing the Exchange ...
    (microsoft.public.windows.server.sbs)
  • Re: Blackberry and MS Exchange Administrator
    ... I understand that you want to install the Exchange ... System Manager components onto a server other than the SBS box. ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange 2003 and NT4 trusted domain
    ... > If you run Exchange 2003, you will need to install AD on at least on ... > use the server for Exchange. ... There would be no need to have a server at the remote ... There is a Linux box at each site ...
    (microsoft.public.exchange.design)
  • Re: Exchange 2003 and NT4 trusted domain
    ... > If you run Exchange 2003, you will need to install AD on at least on ... > use the server for Exchange. ... There would be no need to have a server at the remote ... There is a Linux box at each site ...
    (microsoft.public.exchange.connectivity)
  • Re: Exchange 2003 and NT4 trusted domain
    ... > If you run Exchange 2003, you will need to install AD on at least on ... > use the server for Exchange. ... There would be no need to have a server at the remote ... There is a Linux box at each site ...
    (microsoft.public.exchange.setup)