Common causes to 403 errors?

[bLaCkOuT]

Our company site was working up til a last night when my fellow IT guy, whom hasn't come in yet, played with some IIS stuff on the website server. He doesn't think he did anything that should have changed the site. We all know basically crap about IIS so far.

Now we get a 403 error anytime we try to go there. Anyone know some common causes for it? Trying to figure out what he did.

[Tecil]

Without knowing what he did exactly, and how your IIS server is setup, it's hard to say right off what he could have done.

There are a lot of variables that can happen when someone starts "playing around".

[Tweaker]

Originally posted by bLaCkOuT
Our company site was working up til a last night when my fellow IT guy, whom hasn't come in yet, played with some IIS stuff on the website server. He doesn't think he did anything that should have changed the site. We all know basically crap about IIS so far.

Now we get a 403 error anytime we try to go there. Anyone know some common causes for it? Trying to figure out what he did.

Here is some info

http://www.15seconds.com/issue/020123.htm

[Shalome]

A 403 error means the document you are requesting is "forbidden" -- meaning that you do not have read privileges or are not allowed to have the page sent to you.

If the guy was "playing around," make sure the directory permissions weren't accidentally set to be publically inaccessible. Also, make sure no blocking software was enabled. 403 is a common error code you see when proxy filters are enabled (to keep people from surfing porn, etc).

[bLaCkOuT]

We found out the problem, would take awhile to explain and I'm not even sure I could. Thanks guys.