FP folder permissions don't work

[Guest]

Hi,

I have a Windows 2003 server running IIS, FrontPage 2003, 2002 server exts.
The webs are not under inetpub\wwwroot\ but are in a separate drive for webs
D: There was an OS reload and that's when the problems started. When I use
FP 2003 on my client to set folder properties for webs on the server, the
properties don't work. For instance, if I don't allow files to be browsed,
the files in the folder can be browsed anyway. And when I use FP 2003 on the
server, the folder properties are all non-selectable (grayed out).

I have 3 questions:

1) Does anybody know why the FP folder properties don't work?

I tried uninstalling IIS and FP, manually removing all remaining files
including inetpub\wwwroot\ folders, rebooting server, then reinstalling and
patching. This didn't fix the problem. I also tried using FP 2000 server
exts with FP 2003 (instead of 2002 exts). And I tried this with FP 2000 with
2000 exts, and it's the same problem. Seems like this might be Windows
overriding FP permissions?

2) Does anybody know why the folder properties in FP on the server are all
grayed out and non selectable, while the FP right-click properties on my
client viewing the same webs on the server appears normal?

3) Does anybody know the correct folder permissions to set in Windows
Explorer (since FP permissions don't work) to: A) NOT allow files to be
browsed; and B) allow scripts to be run.

Removing the IUSR\files\read permission and not allowing inherited
permissions on folders don't work. This is for files that contain
configuration data that are used for include files only.

If any of you have any ideas about any of this, I would appreciate your
thoughts.

Thanks,
KF7

 

[Thomas A. Rowe]

Did you re-apply the FP extensions or run a check on them after the re-install of the OS?

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
==============================================
If you feel your current issue is a results of installing
a Service Pack or security update, please contact
Microsoft Product Support Services:
http://support.microsoft.com
If the problem can be shown to have been caused by a
security update, then there is usually no charge for the call.
==============================================

 

[Guest]

Hi Thomas,

Thanks for answering. Yes the FP exts were reinstalled from Windows 2003
Enterprise disk through the Windows Control Panel. Then the exts were
reconfigured in the webs through IIS. I also tried full uninstall of server
exts in webs then reconfiguring them. In fpdadmin.htm the verision number
showing is 5.0.2.6738. I also tried downloading the server exts from MS web
site, instead of using the ones that are on the Windows 2003 disk. But no
luck. Stranage, huh?

Thanks again,
KF7

 

[Thomas A. Rowe]

There are no FP2002 extensions available for Windows 2003, you must use those provided on the CD.

How have you configured IIS to use/manage the webs on Drive D?

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
==============================================
If you feel your current issue is a results of installing
a Service Pack or security update, please contact
Microsoft Product Support Services:
http://support.microsoft.com
If the problem can be shown to have been caused by a
security update, then there is usually no charge for the call.
==============================================

 

[Guest]

Hi Thomas,

The 2002 server exts being used now are the ones that were installed through
Windows Control Panel. The server exts appear to be coming from the Windows
installation disk.

The drive doesn't seem to matter, because the same problem occurs when I
created test webs in the usual c:\inetpub\wwwroot. I tried creating both
server and file based sites and it's the same problem with the FP folder
permissions not working. I tried denying read access to some folders in FP,
but I could access the files in the folders through IE6 through the Internet
and on the server, so the FP folder permissions weren't working.

But this is strange. When I created a test site in FP under localhost on
the server, the right click folder permissions in FP on the server were no
longer grayed out (but still don't work--so I was getting closer to a
solution?). But when I created a file based web, the folder permissiosn are
grayed out in FP on the server but not on FP on my client.

Any thoughts about this? Thanks for your help.

Thanks,
KF7

 

[Thomas A. Rowe]

Are you able to manage the folder permissions (may need to be a subweb site) from within the Server
Extensions Admin?

If you can set them via the OS, then that might be the way to go, but you might also want to spot
this question to the Windows Server or IIS newsgroup, as well.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
==============================================
If you feel your current issue is a results of installing
a Service Pack or security update, please contact
Microsoft Product Support Services:
http://support.microsoft.com
If the problem can be shown to have been caused by a
security update, then there is usually no charge for the call.
==============================================

 

[Guest]

Hi Thomas,

I haven't seen the server exts admin in FP 2003. I'll look for it though.
I think you're right about setting the folder permissions through Windows.
This is a strange problem. I also tried another OS reload and the same
problem occurred before and after Windows and Office patches were applied, so
it must be a default setting in Windows Enterprise that's causing this. I'll
follow your suggestion and search the Windows and IIS groups for this issue.

Thanks for all of your help Thomas. I really appreciate your time.

Best Wishes,
KF7

 

[Thomas A. Rowe]

The server ext admin should be in the Control Panel | Admin Tools.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
==============================================
If you feel your current issue is a results of installing
a Service Pack or security update, please contact
Microsoft Product Support Services:
http://support.microsoft.com
If the problem can be shown to have been caused by a
security update, then there is usually no charge for the call.
==============================================