OWA Secuirty issue

Hi All,

I have, what I hope is a simple permissions issue with OWA.

I thought our OWA was working fine, until I tested it under a non-admin account and found that for general users it would not get any further than the username/password before going to the 401 Access denied page in IE.

I am pretty sure it is all related to permissions, as I said myself and other Domain Admin accounts work with out problems in OWA and when I add a test staff account to Domain Admins it works as well.

Cleary, there is something a miss with OWA permissions - but what I know not. I'd be obliged if some could help out with this issue.

Best wishes and thanks in advance,
Adam.
adamlcohenAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

MesthaCommented:
Reset the virtual directories.
http://support.microsoft.com/default.aspx?kbid=883380
That is always the best place to start.

Simon.
0
adamlcohenAuthor Commented:
Thanks for this, I've gone through the KB steps to recreate the folder but I still have the same problem. I am seeing the following line in the IIS logs for the OWA server:

2009-07-01 11:38:09 W3SVC1 172.16.0.19 GET /exchange - 443 freemens\staff.test 172.16.0.18 Mozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+5.1;+Trident/4.0;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.04506.30;+.NET+CLR+3.0.04506.648;+InfoPath.1;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729) 401 5 0

Is there somehting obvious I am missing ?

Cheers,
Adam.
0
MesthaCommented:
There is nothing in that log to indicate what is going on.
Was that from a working user, or a non-working user?

Simon.
0
adamlcohenAuthor Commented:
Hi,

I've managed to fix this now. For refence the back-end server had the wrong permissions on the DAVEX.dll files. I needed to add Authenticated Users as read/execute access to this file. Stop and restart IIS and all is well now.

Thanks for you efforts prior to this.

Aam.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.