We have an IIS server which hosts an Intranet which we update with MS Frontpage.
We have an issue when trying to create folders with restricted access. The IIS server is using 'Integrated Windows Authentication'. By default when we create a folder under it gives permission to LOCALMACHINE\ADMINISTRATOR amongst others. The strange thing is that this seem to allow all users access to browse this folder. If we move LOCALMACHINE\ADMINISTRATOR from the access on the folder and add the users we want to be able to browse the pages in the folder this works however when we try to edit any of the web pages within the folder from Frontpage it reports the folder as being empty.
If we put LOCALMACHINE\ADMINISTRATOR back into the permissions then we can edit the pages in Frontpage but again it allows all users access.
The strange thing is that some folders within the same allow us to add permissions successfully therefore the issue is not consistent.
One other point to note. If we share the folder through windows explorer the assigned permissions behave correctly.
Any suggestions would be appreciated.
Thanks,
Barry
We have an issue when trying to create folders with restricted access. The IIS server is using 'Integrated Windows Authentication'. By default when we create a folder under it gives permission to LOCALMACHINE\ADMINISTRATOR amongst others. The strange thing is that this seem to allow all users access to browse this folder. If we move LOCALMACHINE\ADMINISTRATOR from the access on the folder and add the users we want to be able to browse the pages in the folder this works however when we try to edit any of the web pages within the folder from Frontpage it reports the folder as being empty.
If we put LOCALMACHINE\ADMINISTRATOR back into the permissions then we can edit the pages in Frontpage but again it allows all users access.
The strange thing is that some folders within the same allow us to add permissions successfully therefore the issue is not consistent.
One other point to note. If we share the folder through windows explorer the assigned permissions behave correctly.
Any suggestions would be appreciated.
Thanks,
Barry