PDA

View Full Version : Desperate OWA Help

Bobba Buoy
12-03-2005, 08:28 AM
Ok I am beside myself now! My OWA was working fine when my exchange server was hosted on the same box as my web server but ever since I moved my web server onto a Windows 2003 Server my OWA "doesn't work". Can anyone please tell me what some of the possible causes for this might be? I really need my OWA!

Thanks a ton in advance!!!!
afterburn
12-08-2005, 12:09 PM
Did you install exchange OWA on the box correctly without exchange then ask exchange to use the connector to connect the store and the AD site?
Bobba Buoy
12-08-2005, 05:49 PM
I am not sure-I did not install it but the guy that did is a professional. And it worked until I moved the web server to a seperate box.
afterburn
12-08-2005, 11:12 PM
OWA must be on the Exchange Server. To setup correctly you should use Exchange 2003. And follow the wizard for RPC server setup to allow distributed services. and multiple exchange servers with only 1 frontline server.
NerdLib
12-09-2005, 11:23 AM
Also make sure that the IIS services are configured properly and are not denying access.

Can you tell us what is hapening exactly?

I am an Exchange admin on over 15 machines with some complexe setups so this seems like it is something really silly.

Such as the OWA VD is pointed at the worng location or does not have permissions.

Check the event viewer and paste back to me.
afterburn
12-09-2005, 11:33 AM
IIS Directory for exchange is configured by default to have NTLM permissions prompt for creditals.
NerdLib
12-09-2005, 01:16 PM
But this does not mean it was accidently changed or directory was changed or permissions were changed.

Just a starting point. We don't have any errors to trobuleshoot so it is a shot in the dark.
afterburn
12-09-2005, 04:34 PM
Well the creditals not being suppiled would be an error, 403. As they are data that is using Impersonation. Its a security creditial setting that is built into it. Look into SecurityDescriptor.
Bobba Buoy
03-12-2009, 04:55 PM
All I know is it used to work when the exchange and the web server were on the same box (ie: same ip address) but now that they are on seperate stations it doesn't work. As I understand it, it has something to do with needing to reserve an ip address for the owa. I have a block of ip addresses so that shouldn't be a problem but I don't know how to set it up.