Re: Front end server OWA redirection
From: Ben Winzenz [Exchange MVP] (ben_winzenz_at_NOSPAMdotmessageonedotcom)
Date: 03/02/05
- Next message: you know who maybe: "Ontrack PowerControls ???"
- Previous message: NetGoofy: "Multiple Storage Groups and Databases"
- In reply to: Grant: "Re: Front end server OWA redirection"
- Next in thread: Ben Winzenz [Exchange MVP]: "Re: Front end server OWA redirection"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 2 Mar 2005 10:59:46 -0600
No - misunderstanding.
The OWA Logon page isn't available until you enable Forms-based
authentication (and configure SSL). However, even without FBA in place,
entering the URL of the FE server and entering your login information (in
the password prompt box) should show your mailbox on the correct BE server.
Basically, being able to view the logon page requires additional
configuration, but the redirection to the correct BE does not. Make sense?
Also, look for my post with the exact details of my config here. That
should be coming along shortly (as soon as I finish typing current settings
for my config).
-- Ben Winzenz Exchange MVP "Grant" <gpsnett@hotmail.com> wrote in message news:OB9VFR0HFHA.3072@tk2msftngp13.phx.gbl... > So let me get this straight, with the test front end I installed: > > 1. Without any further configuration I should see the default owa login > page? > 2. Without any further config I should be redirected to the BE server > automatically? > > So then how come on both my FE servers, the OWA login page is not > displayed by default? I had to first follow these instructions on the one > FE test server to see the page: > http://support.microsoft.com/default.aspx?scid=kb;en-us;555053 > > Some additional info that might be causing this is that I never specified > the FE as an FE server or the BE as a BE server. I only modified some > registry settings that allows certain ports on certain servers to be used. > I couldnt get RPC-HTTP to work any other way! > > > "Ben Winzenz [Exchange MVP]" <ben_winzenz@NOSPAMdotmessageonedotcom> wrote > in message news:uPmvvD0HFHA.4032@TK2MSFTNGP12.phx.gbl... >> You might try adding the cert to IE's certificate store on your computer. >> I'll also pull up my lab environment here and see if there are other >> specific settings enabled. >> >> -- >> Ben Winzenz >> Exchange MVP >> >> >> "Grant" <gpsnett@hotmail.com> wrote in message >> news:ezejwyzHFHA.2700@TK2MSFTNGP09.phx.gbl... >>> FE and BE server are both on the LAN. SSL is configured on the FE server >>> only. >>> Going directly to the backend server gets me a login prompt - Entering >>> domain\username and password, I can see my inbox via OWA. >>> >>> I checked those IIS permissions and they are as you suggested. >>> >>> Ive got a new front end test server configured with: >>> SSL >>> RPC-HTTP working. >>> >>> With this new FE server, if I browse to the https://Servername/exchange >>> Im asked to trust the certificate, then get an 'Cannot find server or >>> DNS Error' >>> >>> With the old test server if I browse to https://Servername/exchange, Im >>> asked to trust the certificate, then I get the Login page where I can >>> select a premiums or basic login. When I enter my details with an >>> incorrect password I get an error saying: >>> >>> 'You could not be logged on to Outlook Web Access. Make sure your >>> domain\user name and password are correct, and then try again.' >>> >>> And when I enter the correct details I get the 'Cannot find server or >>> DNS Error'. >>> >>> Im no longer getting the 400 error.... its still going to the >>> https://servername/exchweb/bin/auth/owaauth.dll >>> >>> >>> >>> "Ben Winzenz [Exchange MVP]" <ben_winzenz@NOSPAMdotmessageonedotcom> >>> wrote in message news:O0FoSmzHFHA.580@TK2MSFTNGP15.phx.gbl... >>>> Where is your FE server? DMZ or internal LAN? Do you have SSL >>>> configured on both the FE and BE? (you should only need it on the FE). >>>> Redirection to the appropriate BE server should be done automatically. >>>> >>>> What happens if you go directly to the address of the BE server? >>>> >>>> Also, check your permissions in IIS. On the FE server, you need to >>>> make sure you have the following: >>>> >>>> Front End: >>>> Exchweb Vdir - Anonymous >>>> Exchweb/Bin - Basic >>>> >>>> Back End: >>>> Exchweb Vdir - Anonymous >>>> Exchweb/Bin - Basic AND Integrated >>>> >>>> -- >>>> Ben Winzenz >>>> Exchange MVP >>>> >>>> >>>> "Grant" <gpsnett@hotmail.com> wrote in message >>>> news:ObMkSwyHFHA.3588@TK2MSFTNGP14.phx.gbl... >>>>> Hi, >>>>> >>>>> I have configured a front end server to use RPC-HTTP successfully. Ive >>>>> got the SSL certificate and it all works great. >>>>> Problem is, Im trying to configure an Outlook web login page, but cant >>>>> get it to redirect to the backend server. Firstly I wasnt even getting >>>>> an OWA page until I followed the instructions in the this article: >>>>> >>>>> http://support.microsoft.com/default.aspx?scid=kb;en-us;555053 >>>>> >>>>> Now I get a login page but as soon as I type in a domain\username and >>>>> password, I get a 404 page could not be found error. This should be >>>>> redirecting to my backend server (Where OWA is working fine) but i >>>>> notice in the address bar it says; >>>>> >>>>> https://Servername/exchweb/bin/auth/owaauth.dll >>>>> >>>>> So what else am I missing here? How do i get this redirected to my >>>>> backend server? >>>>> >>>>> Any help greatly appreciated! >>>>> >>>>> Cheers, >>>>> Grant >>>>> >>>> >>>> >>> >>> >> >> > >
- Next message: you know who maybe: "Ontrack PowerControls ???"
- Previous message: NetGoofy: "Multiple Storage Groups and Databases"
- In reply to: Grant: "Re: Front end server OWA redirection"
- Next in thread: Ben Winzenz [Exchange MVP]: "Re: Front end server OWA redirection"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
