microsoft.public.exchange.admin

Ah, right. Not so much a logon failure, as some kind of crash at the server
end. Does it say anything else about the 500 error? If not, make sure you
have 'Friendly HTTP Errors' disabled in your browser. Also, is there
anything written to the Event Log (application) on the server?

"Rick Thornberry" wrote in
message news:CE26C85A-69E4-45EC-8CFA-8C870F1AE7AA@microsoft.com...
> Basic and windows integrated. They get 'the page cannot be displayed' with
> http 500 error - internal server error.
>
> "Lee Derbyshire [MVP]" wrote:
>
>> What kind of authentication are you using for OWA (Basic, Integrated,
>> Forms-based), and what happens when they try to logon?
>>
>> "Rick Thornberry" wrote in
>> message news:7496BB65-70F0-45DB-940D-3882A4E6C814@microsoft.com...
>> > Lee-
>> > 2000 Server with Exchange 2003 Enterprise. We added the exchange server
>> > (where owa resides), to the list of computers and it didn't help.
>> > -Rick
>> >
>> > "Lee Derbyshire [MVP]" wrote:
>> >
>> >> "Rick Thornberry" wrote in
>> >> message news:B3729548-2733-436E-A749-7E4F7428E15B@microsoft.com...
>> >> > We want to add a layer of security via the "Logon to the following
>> >> > computers"
>> >> > parameter in each user's active directory account tab. That works
>> >> > great,
>> >> > but
>> >> > prohibits users from logging on to owa from the outside since we
>> >> > won't
>> >> > always
>> >> > know the computer name of the remote computer they are using. Is
>> >> > there
>> >> > a
>> >> > way
>> >> > to get around that?
>> >> > Thanks,
>> >> > Rick
>> >>
>> >> Which Server and Exchange version do you use? Since OWA is an IIS
>> >> application, your users may need logon rights to the OWA server
>> >> itself.
>> >>
>> >> Lee.
>> >>
>> >> --
>> >> _______________________________________
>> >>
>> >> Outlook Web Access for PDA, OWA For WAP:
>> >> www.leederbyshire.com
>> >> ________________________________________
>> >>
>> >>
>> >>
>>
>>
>>