I'm finally trying to move my Links 2.0 setup from my prototyper to my public site.
Everything is nice and stable on the prototype site, but when I try to open admin.pl on the public site, I get an error that reads:

"403.2 Forbidden: Read Access Forbidden

This error can be caused if there is no default page available and directory browsing has not been enabled for the directory, or if you are trying to display an HTML page that resides in a directory marked for Execute or Script permissions only."

In IIS 4 I've tried adding browse permission to the Links admin dir. I've told it to accept admin.pl as a form of default file.

Still doesn't work. Any suggestions?

TIA

Bobb Menk

Solved my own problem - Perl was associated with the pl extension at the NTFS level, but IIS 4 needed an explicit configuration for this as well in the application settings for the scripts dir. FWIW the fix requires you to configure application settings, app mappings, with the full path to the perl executable followed by two %s arguments:
c:\perl\bin\perl.exe %s %s and then fill in pl for the extension in the appropriate box in the form.

Bobb Menk