2003 OWA re-prompts user with HTTP header host name\username after installing KB916803

Posted on 2006-05-14
Last Modified: 2012-05-05
Prior to installing KB916803, we had 2003 OWA and IIS set to redirect to SSL then prompt the user for a username and password and ASSUME the domain name.  After installing this fix, the user enters his/her username and password and IIS re-prompts with the host name used in the URL header implied as the domain, not the actual organizational domain we had set as the default.  Any ideas would be appreciated.
Question by:dsrumer
    LVL 5

    Expert Comment

    What if you re-define the default domain name and realm in the properties in IIS? Maybe you just setting that info again will update the IIS metabase to use the correct info.

    Author Comment

    Tried that prior to posting question and just tried again with no luck.  Also tried modifying the settings in Exchange System Manager/Servers/Protocols/HTTP.

    The thing I can't figure out is why IIS is prompting with the Internet name of the host and not the actual domain or IIS host name domain i.e. versus  The way it WAS working, the internal domain name "COMPANY" was defaulted and all the user had to do was enter their username.  Now, it seems like IIS is trying to validate their profile on a non-existant domain.

    Author Comment

    However, when I enter COMPANY\username and password, login is successful.
    LVL 18

    Expert Comment

    Try this:

    Title: Exchange 2003 OWA - Don't want to type domain\username at prompt
    LVL 7

    Accepted Solution


    Author Comment

    Amaheshwari, thanks for the link, which I studied.  I really do not want to change the way users log on at this time.

    Vasant, thank you too for the link.  I had already studied article 903924 but had not followed the instructions to the letter.  I unchecked Integrated Windows Authentication in the properties of the Exchange Virtual Server and it began working as before.

    What confuses me is that the previous setting had worked for at least a year AND I have the previous setting functioning on other servers for other customers and it is working fine.  I can only assume that KB916803 made a change to how this functions and I have not applied the fix to the other servers.

    Featured Post

    How your wiki can always stay up-to-date

    Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
    - Increase transparency
    - Onboard new hires faster
    - Access from mobile/offline

    Join & Write a Comment

    Use these top 10 tips to master the art of email signature design. Create an email signature design that will easily wow recipients, promote your brand and highlight your professionalism.
    ADCs have gained traction within the last decade, largely due to increased demand for legacy load balancing appliances to handle more advanced application delivery requirements and improve application performance.
    In this video we show how to create an email address policy in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Mail Flow…
    The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…

    731 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    15 Experts available now in Live!

    Get 1:1 Help Now