>I have a VFP COM Server running under WC successfully on a development server in the Intranet. When the application was moved to the production server, IIS issues a challenge when an attempt is made to fire the COM server, whether from a web page link or if I type in a URL to a test method in the server.

Is it the .dll link that causes this or the COM server permissions? I think it's the DLL permissions, cause you wouldn't get an auth box in the browser if the server failed due to access rights.

That leaves you with the issue of incorrect directory permissions. Check and make sure that the IUSR_ account has execute rights whereever wc.dll lives and script rights in whatever directory you try to access any script map pages. Also make sure you got your application isolation mode in IIS set to Low - if you use the default Medium the account you need to mark will be IWAM_ instead of IUSR_. Sometimes permissions can get wacky on NT/2000 so remove those accounts and add 'em back in.

Make sure basic auth/ntcr are enabled ofr all the directories in question. The DLL path as well as the virtuals you're running out of (if different).

+++ Rick ---