Discussion Locked

OWA won't let other domains in

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Exch 5.5 w/ SP3, NT4.0
I just moved my OWA from a separate server to the exchange server itself. Now all of the sudden only users that are part of the domain that the server is in can get in.
Log on Locally & Access computer from network permissions are granted to Everyone. All of the basics seem to be covered (I think?).
Everyone gets their mail fine. This is strictly an OWA problem.

5 replies

by lordinfidel

This is a limitation of installing the OWA on your exch srvr.

It will only validate user names belonging to that domain, as you can now see you no longer have to put in domain\username, just username.

Best Practices for exch stronglyt discourage putting the OWA on the exch srvr. For every person who connects to the OWA, a seperate outlook process is spawned. If you have multiple people connecting at the same time, this will eat up system resources.

Also this becomes a security risk by allow outside access over other ports than 25. Lock down your exch srvr to only what it needs, remove IIS, index server, etc.

by tmiller3

It now works....
I had to check the NT Challenge Response box in addition to the Basic Authentication box. I also found that the IUSR_servername account had been deleted and not recreated. Now it works, but changed to separate name/pswd/domain boxes instead of just name/pswd as before.

by brasslet

RE: #1...there is no "limitation" regarding OWA and other domains on an Exchange server. I know this because I can open users' mailboxes in other domains from an Exchange server in my domain using OWA. Also, nothing in TechNet etc. describes such a limitation.

Re: the original problem...you're on the right track. This is a permissions or user rights issue. Look at the OWA directory permissions as well. KnowledgeBase articles Q248486 and Q175892 have more detailed information about the rightsand permissions needed to access OWA.

While #1 is incorrect re: OWA on the Exchange server, he's got some good points about other concerns running OWA etc. on it.

by tmiller3

It now works....
I had to check the NT Challenge Response box in addition to the Basic Authentication box. I also found that the IUSR_servername account had been deleted and not recreated. Now it works, but changed to separate name/pswd/domain boxes instead of just name/pswd as before.

This discussion is closed to new replies.