>Without more information, it is hard to tell what the problem might be. I suggest you setup auditing for Object Access and LogOn/LogOff Failures (don't use Success, as it will clutter your event log) on all the website's directories (if they are large it may take a few minutes to apply), or at least the obvious directories being accessed. Then try to access the site via the browser, and after that check the Security Event Log on the web server machine. Hopefully, it will show you where the access is being challenged and you can check permissions on the resource(s) indicated. If you don't see any events resulting from your access attempt, you can always set auditing on the WINNT directory. If you are using any sort of dynamic content (as WC produces), you might be trying to access DLLs or other system files that might not be too obvious, and might not have correct permissions set for them. Usually these are stored in the WINNT folder/sub-folders. Finally, audit the installation
>directory of WC to see if there's anything there that's being accessed. If you are not familiar with setting up auditing on NT, contact me offline and I can help you with that.
>
>Good luck!

We contacted MS and described the situation to them. It turns out that the URL set up for the Intranet site has periods (.) in it similar to an Internet site. IIS scans the URL and if it sees periods it "assumes" it is an Internet site and automatically challenges. Not good. The fix is to add the site to the list of Intranet sites in IE Internet Options, Security, Intranet Security data.