Web Publishing Results in 401 Unauthorized

Hi folks!

I have been running ISA 2004 for years but have not worked with it lately (it is
been good!)
Anyway, I just moved my website back to my network and while it works
internally logging seems to show nothing but 401 Unauthorized for external
requests.

I have looked at the publishing rule and all looks well. If memory serves this
was a common occurrence that people ran into. What am I doing wrong?
The site is located at http://www.askmarvin.ca/forums/index.php if anyone
wants to check it.

Any and all help is appreciated - it is probably something simple I have
forgotten over the years (gasp!)

Thanks!

Just as an update - it appears that when visiting the site I am presentedwith

Just as an update - it appears that when visiting the site I am presented
with the username/password box but if I click cancel twice the website shows
up! The exact error message I got was http 401.3 Access denied by ACL on
resource.

Yuk!

It appears to be an issue with the web server as opposed to ISA :-(Oh well, I

It appears to be an issue with the web server as opposed to ISA :-(

Oh well, I just did a format/re-install so we will see shortly :-0

ArgghhhhhH!!!!!!

ArgghhhhhH!!!!!!

it is not an IIS issue - I just did a complete re-install of the web server
and guess what? Same thing :-(

If anyone has any ISA ideas, please let me know...

OK, after much messing around I finally figured out what was wrong.

OK, after much messing around I finally figured out what was wrong.
I doubt anyone will ever encounter the same issue but for future reference
here is what caused the 401.3 errors.

I took down a large web site that I had up and running for many years.
Instead of keeping all the content, I archived it off, but of course traffic
still came to the site and this resulted in tons of 404 errors due to the
missing site.

So, what I did was put up a single static HTML page explaining that the site
was retired and thanking everyone for their years of use. My thoughts were
that all the search engines and people would see this and that would update
all the indexes with that one HTML page.
Good enough, but here is what happened - I still got a ton of 404's from
external traffic looking for pages that no longer existed.

This is where I introduced the problem and it was not ISA.
I went into IIS and changed every error page for that site to display the
single HTML file I had created. In this way, whenever anyone requested
anything that did not exist or resulted in any error they would be shown the
single HTML file explaining that the site was retired.

By doing that I introduced the error. I do not understand the mechanics
behind it but once I set all the IIS error pages back to their stock
settings all the 401.3 errors went away. Looking back on it, that was the
only change that was made since the site was active - so it made sense.