Re: OWA not authenticating

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

From: Ben Winzenz [Exchange MVP] (ben_winzenz_at_NOSPAMdotmessageonedotcom)
Date: 03/24/05 

Date: Thu, 24 Mar 2005 12:15:52 -0600

You don't need to worry about letting the BE server know. I also don't
think that the domain\realm settings would be causing issues - the realm
information isn't used with Basic authentication anyways. At least not
according to the IIS Help file.

I don't see anything else out of the ordinary with the auth settings. You
may need to submit a PSS incident about this.

Regarding the owaaps thing, I've written an article that details how to get
that working (if you want to make it work).
http://www.techtidbits.net/html/owa_security.html 

-- 
Ben Winzenz
Exchange MVP
"Grant" <gpsnett@hotmail.com> wrote in message 
news:Oe2HTGJMFHA.1172@TK2MSFTNGP12.phx.gbl...
>I have 2 FE servers - the 1st one is a test server and the 2nd is the live 
>one which everyone is now using for RPC-HTTP. I was playing around with 
>settings on the test server (googling around getting suggestions and 
>workarounds from different places) and managed to get OWA working fine, and 
>it still is - but now I dont know what I did that made it work!
>
> Anyway here are the IIS authentication settings from the faulty server 
> (Same settings as the working one):
>
> Exadmin - Integrated Windows Authentication
> Exchange - Basic Authentication (Passwords sent in clear text)
> ExchWeb - Anonymous
> MS Server active sync - Basic Authentication (Passwords sent in clear 
> text)
> OMA - Basic Authentication (Passwords sent in clear text)
> Public - Basic Authentication (Passwords sent in clear text)
> RPC - Basic Authentication (Passwords sent in clear text) and Integrated 
> Windows Authentication
>
> Do I need to let the main BE Exchange server know about each FE server 
> that connects to it? The only differences between the two FE servers is 
> that on the test server, I set up this 'owaasp' thing that redirects HTTP 
> requests to HTTPS automatically (Supposed to  - it didnt work for me), and 
> under most of the virtual directories, the test server has no 'domain' or 
> 'realm' specified but the other FE server (the one thats not working) 
> does...
>
>
> "Ben Winzenz [Exchange MVP]" <ben_winzenz@NOSPAMdotmessageonedotcom> wrote 
> in message news:e0TLVqIMFHA.2464@TK2MSFTNGP10.phx.gbl...
>> Can you verify and post the authentication methods that you have set up 
>> for the /Exchange, /exchweb virtual directories in IIS on both the FE and 
>> BE servers?
>>
>> For example, do you have Basic, Integrated set?  If so, on which of those 
>> directories on each server.  This definitely sounds like some sort of 
>> permissions issue, so listing the auth methods should help identify 
>> what's going on.
>>
>> -- 
>> Ben Winzenz
>> Exchange MVP
>>
>>
>> "Grant" <gpsnett@hotmail.com> wrote in message 
>> news:uav8ETGMFHA.3196@TK2MSFTNGP10.phx.gbl...
>>>I have a front end Exchange 2003 which has SSL and is configured 
>>>correctly to use RPC-HTTP. Thats all working fine. Problem is OWA. I can 
>>>get to the front end page and it asks for username and password, but 
>>>after entering those details it thinks for a few seconds and then comes 
>>>back with 2 frames both containing the login and password boxes. I get no 
>>>error message or anything, it just reloads these frames asking for my 
>>>credentials.
>>>
>>> The page looks like OWA should, in the left frame there should be my 
>>> email tree, and in the right frame there should be whatever I have 
>>> selected in the left pane - but not for me - I just get the password 
>>> boxes.
>>>
>>> Thanks for any help,
>>> Grant
>>>
>>
>>
>
>

Relevant Pages

  • Re: OWA not authenticating
    ... PSS is Microsoft Product Support Services. ... >> You don't need to worry about letting the BE server know. ... >> information isn't used with Basic authentication anyways. ... >>> MS Server active sync - Basic Authentication (Passwords sent in clear ...
    (microsoft.public.exchange.connectivity)
  • Re: OWA not authenticating
    ... PSS is Microsoft Product Support Services. ... >> You don't need to worry about letting the BE server know. ... >> information isn't used with Basic authentication anyways. ... >>> MS Server active sync - Basic Authentication (Passwords sent in clear ...
    (microsoft.public.exchange.admin)
  • Re: Accounts locked out
    ... You may want to look at two things on your server: ... In this article see the first two settings: ... Run SuperScan and go to the Windows Enumeration tab. ... way they get your user names and then try and break the passwords. ...
    (microsoft.public.inetserver.iis)
  • Re: Changing systems
    ... >> settings, and passwords remain the same as they currently are on the ... > I also forgot to mention that I would like to copy users crontabs over. ... the to new server to behave like the old one anyway. ...
    (comp.unix.bsd.freebsd.misc)
  • Re: OWA not authenticating
    ... You don't need to worry about letting the BE server know. ... information isn't used with Basic authentication anyways. ... I don't see anything else out of the ordinary with the auth settings. ... > MS Server active sync - Basic Authentication (Passwords sent in clear ...
    (microsoft.public.exchange.admin)