Exchange 2003 and ASP OWA

[g0kuss4]

Hi guys, I'm experimenting with Exchange 2003, and I can't seem to get the OWA running though the form. I am able to log in through OWA, just not use the nice little web page. I am only able to login with a windows auth. Can anyone help me out, getting the OWA to work?

This is what I want to use to login.

and when I click "Log On" it sends me to this "page"...

http://www.site.com/exchweb/bin/auth/owaauth.dll

 

[racosta70]

I tried the same process on our Exch2003/OWA site but I get the "HTTP 500 - Internal server error Internet Explorer". Trying to resolve it but will let you know if I find out how.

 

[pvalent307]

Note that following Step 2 of the following procedures solved my problem with this same error on Exchange 2003 OWA. Specifically the part about If a Create button is displayed next to the Application name box, click it. Exchange then appears in the Application name box.

Step 1: Verify Exchange Virtual Directory Settings
Start Exchange System Manager. To do this, click Start, point to Programs, point to Microsoft Exchange, and then click System Manager.
Expand Servers, expand ServerName, expand Protocols, expand HTTP, and then expand Exchange Virtual Server.
Under Exchange Virtual Server, right-click the Exchange virtual directory, and then click Properties.

Important Make sure to verify Domain Name System (DNS) settings and to verify the e-mail domain of the user who is experiencing this issue. If the e-mail domain is set incorrectly, you can resolve this problem by setting the e-mail domain correctly.
Click the Access tab, and then click Authentication.
Click to select the Basic authentication check box, if it is not already selected.
In the Default domain box, type \ (the backslash character), if it is not already present.
Click OK, click OK again, and then quit the Exchange System Manager snap-in.
Step 2: Verify Default Web Site Properties
Expand Default Web Site, right-click the Exchange virtual directory, and then click Properties.
On the Virtual Directory tab, verify that the Local Path box points to the M drive, and then make a note of the path.
Verify that the Application name box contains the Exchange virtual directory application.

NOTE: When a valid application is displayed in this box, the Create button is not displayed. Instead, a Remove button is displayed next to the Application name box. If a Create button is displayed next to the Application name box, click it. Exchange then appears in the Application name box.
Click the Directory Security tab, and then click the Edit button under Anonymous access and authentication control.
Click to select the Basic authentication (password is sent in clear text) check box, if it is not already selected.
Under Authenticated access, click the Edit button.
In the Domain Name box, type \ (backslash character) if it is not already displayed.
Click OK, click OK, click OK, and then quit the Internet Information Services snap-in.
Step 3: Verify Exchange Recipient Policy
Start Exchange System Manager.
Expand Recipients, and then click Recipient Policies.
In the right pane of the Exchange System Manager window, view the Properties pages of the recipient policies to determine if an SMTP address that corresponds to the folder in the M drive (which you noted earlier in step 6 of "Verify Default Web Site Properties&quot is listed on the E-Mail Addresses (Policy) tab.
In the left pane of the Exchange System Manager window, click Recipient Update Services under Recipients.
In the right pane, right-click Recipient Update Service (Enterprise Configuration), and then click Rebuild. Click Yes to confirm this operation.
Right-click Recipient Update Service (Enterprise Configuration), and then click Update Now.
Right-click Recipient Update Service (DomainName.com), and then click Rebuild. Click Yes to confirm this operation.
Right-click Recipient Update Service (DomainName.com), and then click Update Now.
Quit the Exchange System Manager snap-in.
Wait for a few minutes to allow the Rebuild opeartion and the Update operation to complete, and then test Outlook Web Access (OWA) from a client computer.