Link to home
Start Free TrialLog in
Avatar of Member_2_4400838
Member_2_4400838

asked on

HTTP Error 403.1 Forbidden - I believe the issue lies with IIS but how tofix........

We have a server that until the beginning of this month was working well, when doing some regular maintenance checks (its off site from our main office) we noticed we could access the web console for AV reports, we kept getting HTTP Error 403.1 - Forbidden: Execute access is denied.  I figured the problem was with the AV software so a uninstall and reinstall eventually fix that.  However after this we were looking at the usage stats for exchange in the server management window of SBS 2003, and started getting the same errors, we now have reports of users unable to access outlook web access with the same error.  I believe the problem is with IIS somewhere but not sure where to start looking.  Any suggestions would be appreciated.
SOLUTION
Avatar of top_rung
top_rung
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Member_2_4400838
Member_2_4400838

ASKER

Hi guys,

have appreciated the assistance, I was in the process of reading through adn about to start the solution offered by toprung, when K_nitin_r 's post came through, i'm sure top rungs would have provided the same result, however K_nitin_r has fixed the OWA issue....

However when I try to view web based reports in the Server managment such as monitoring and reporting I still get the error, I'm sure setting the execute permissions to script only or script and executables will fix this but I'm not sure which website/virtual directory I should do this on for this function?  any suggestions?
scratch my last comment, i think i've found it... thanks for your assistance
Glad you found things out.  Grab that resource kit for sure!!!

Thanks for the timely responses guys, as I said in the question I suspected it was with IIS and had tried a few config changes myself but didn't want to break it further.

Good work!  Greatly appreciated