Unable to access OWA 1

[joelrob]

I have a 2000 server running Exchange 2000 sitting behind a Symantec Firewall. Right now our e-mail is hosted by a third party and downloaded to our Exchange Server via third party software. We're preparing to host our own domain and e-mail and I wanted to test everything to make sure it works before we take the jump. I am able to access the website remotely by typing in the static IP of our server, but I am unable to get to OWA. I get a "user not authorized" error when I try. When the login prompt comes up I am using the exchange alias and password to login, which is also the domain login. Any suggestions?

Thanks.

 

[tangostar]

1. can you access it properly from inside the network?
2. try using DOMAIN\username format for your username.

 

[joelrob]

No, I cannot access from inside the network either. I have tried using the Domain\Username, alias name, mailbox name, Administrator name/password, everything.

 

[tangostar]

could you ever access OWA?

 

[joelrob]

It's never been tried before. This is an initial configuration. Exchange was installed about 2 months ago, a clean install with all default settings.

 

[tangostar]

well then you're going to have to configure IIS on the server.
It shouldn't take long, i'll see if i can find a Help Post.

 

[tangostar]

Ehhh. srew it I can't find it. Just do this.
Open IIS
Right Click Default Web Site (that's OWA unless you've changed it) goto Properties
Directory Security
check only Anonymous access
OK
Home Directory
A redirection to a URL
Redirect to /exchange

check a directory below this one
OK

Expand Default Web Site
properties of Exchange
Directory Security
Check only Basic Authentication, Insert Domain name of \ yes just "\"
OK
do the same for public, and Exadmin


Then one last thing if it still doesn't work. Give Domain Users "Logon Locally" Permission.

You should also consider using a certificate to encrypt this page. But you can worry about that after you get it up and running.

 

[joelrob]

If I redirect the home directory to /exchange, will this stop users from accessing the main webpage? Our website will be hosted on this server as well. Do I need to create a new site for OWA and direct it there?

 

[tangostar]

you should have the two seperated anyways, just avoid confusion. You can have multiple site on the one machine if you use host headers.
But if you don't want to do the redirect, I guess technicaly you don't have too. The difference is that if you do then clients only have to type in the FQDN like mail.company.com where as right now they have to do mail.company.com/exchange.

 

[joelrob]

I understand, but typing in the IPAddress/exchange should get me there, which is what I'm doing now. It's coming up with the login, for some reason the login is just not authenticating properly. When the login comes up, I have tried DOMAIN\USER, USER@DOMAIN.com, every combination I can think of. I have checked the event viewer, there are no error logs there. Does anyone know of any logging that has to be enabled to make the failed attempts show up? Something should be showing.

 

[tangostar]

have you made the other changes I suggested? Other then the redirect?
You can also open System Manager browse to the server open the HTTP protocol and set the security on the virtual folders there. This setting takes president.

 

[joelrob]

Yes, I made all the other changes, even went ahead and set the redirection. Same thing. I've tried my personal login, the Administrator login, neither is working. In the ESM all settings are disabled, a note says changes must be made from IIS.

 

[tangostar]

Yes if you try to look at the properties or make changes to the virtual server you will get that message. If you expand the serer and look at the virtual directories you can make changes.