Re: security control IWAM_myserver

From: Jeff Cochran (
Date: 08/26/04

Date: Thu, 26 Aug 2004 17:53:22 GMT

On Thu, 26 Aug 2004 15:55:06 +0100, "Chun Wong"
<> wrote:

>Thanks Jeff for you reply.
>The web application is Perl CGI on IIS6
>I intended to use the windows integration authentication on IIS
>no matter administrator or anyone is member of IIS_WPG group, they would be
>able to access to the perl script.
>they will get the "you are not authoristed to view this page" http error 403
>There is only one user account can successfully access to those perl script
>which is "IWAM_myservername"

Check permissions on the Perl DLL (or Perl.exe if you use that).
Check permissions on the file/folder the script is working in. Check
the command line interpreter on the server to see if that group or
user has access.


>"Jeff Cochran" <> wrote in message
>> On Thu, 26 Aug 2004 10:52:33 +0100, "Chun Wong"
>> <> wrote:
>> >I got a windows 2003 STD and currently running as AD, IIS6 which is
>> >some Perl script. Active Perl been installed
>> >
>> >All the Perl scripts are *.pl extension and hosted on IIS6 and the client
>> >browser is IE6
>> >
>> >All my *.pl scripts are only working under "IWAM_Myservername" account
>> >will not work under any other accounts on Client browser IE6
>> >
>> >I add myself to the IIS_WPG group but I am still not able to access those
>> >*.pl scripts and keep getting http error 403 on IE6
>> >
>> >Local secruity setting are everyone full control.
>> >
>> >
>> >anyone got the idea?
>> Assuming you're using Windows Integrated authentication, create a
>> group that can run Perl and assign that group permissions to the Perl
>> DLL (or whichever Perl you're using). Naturally they need permissions
>> to do whatever your script does as well, but you'd see those problems
>> in the error message you didn't post when you didn't describe what
>> "will not work" actually means.
>> Jeff