Re: Exchange 2003 OWA front page

  • From: <Paul_Lemonidis@xxxxxxxxxxx>
  • To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
  • Date: Thu, 26 Aug 2004 14:20:09 +0100

Hi All

Further to my post I forgot to say. I have enabled  forms based autenticationas 
as in the relavant part of TechNet article 830827. It has made no differnece. 
Could this be a firewall issue?

I am just totally stumped now. Any help gratefully recieved.


Paul Lemondis.

  ----- Original Message ----- 
  From: Paul_Lemonidis@xxxxxxxxxxx 
  To: [ExchangeList] 
  Sent: Thursday, August 26, 2004 1:39 PM
  Subject: [exchangelist] Exchange 2003 OWA front page

  Hi all

  I think I know the answer to this but just need to know if I am correct and 
what to do if I am. I am guessing and I must admit it is a guess at this stage 
that this is something to do with forms based authentication.

  I have setup a test Windows\Exchange 2003 box on a test network behind a 
different firewall to our normal network (the test firewall is a Watchguard 
Soho box) with an MX record pointing to an address in our external subnet which 
is duly assigned as the external address of the SOHO box. Hence the test box 
can send and receive mail fine on its test MX record. 

  All the changes for full SSL based CA web access have been implemented. The 
OWA interface works with one exception. Instead of getting the nice Exchange 
2003 page when I first go to the site I just get a logon box and nothing else 
as in Exchange 5.5. After logging on all is fine. What, if anything, have I 
done wrong and how can I correct this please?

  Many thanks in advance.


  Paul Lemonidis.
  List Archives:
  Exchange Newsletters:
  Exchange FAQ:
  Other Internet Software Marketing Sites:
  World of Windows Networking:
  Leading Network Software Directory:
  No.1 ISA Server Resource Site:
  Windows Security Resource Site:
  Network Security Library:
  Windows 2000/NT Fax Solutions:
  You are currently subscribed to this Discussion List as: 
  To unsubscribe visit
  Report abuse to listadmin@xxxxxxxxxxxxxx 

Other related posts: