Article ID: 324067 - Last Review: October 30, 2006 - Revision: 3.4 HOW TO: Set Folder Security for Shared FoldersThis article was previously published under Q324067 NoticeThis article applies to Windows 2000. Support for Windows 2000 ends on July 13, 2010. The Windows 2000 End-of-Support Solution Center (http://support.microsoft.com/?scid=http%3a%2f%2fsupport.microsoft.com%2fwin2000) is a starting point for planning your migration strategy from Windows 2000. For more information see the Microsoft Support Lifecycle Policy (http://support.microsoft.com/lifecycle/) .NoticeThis article applies to Windows 2000. Support for Windows 2000 ends on July 13, 2010. The Windows 2000 End-of-Support Solution Center (http://support.microsoft.com/?scid=http%3a%2f%2fsupport.microsoft.com%2fwin2000) is a starting point for planning your migration strategy from Windows 2000. For more information see the Microsoft Support Lifecycle Policy (http://support.microsoft.com/lifecycle/) .On This PageSUMMARY
This article describes how to set sharing permissions on a Windows folder that is being used to hold Web site information. The permissions affect how other users can access the files over a Network File System (NFS) or Server Message Block (SMB) share, but they do not affect how users access the files and folders in Internet Information Services (IIS). Translating UNIX Permissions to WindowsMost UNIX platforms use a simple user/group/other and a read/write/execute combination to set permissions for a specific file or folder. For example, you can set permissions on a file so that it is readable by everybody, but writable only by the user and group owner. There is also some specific behavior in UNIX, for example, users can only access the contents (or the list of files and folders) for folders that have Execute permissions. Additionally, UNIX uses the Execute permission bit on files to identify those files that can be run. If UNIX recognizes the file as a binary file, the file is run as a native binary. If the file is a text file, UNIX looks at the first line to check which program is used to run the file.The Windows model is a little different (however, the basics concepts are the same). In Windows, files and folders can have Read and Write permissions, but these permissions are granted explicitly to individual users or groups of users instead of to the owner, the group owner, or everybody. You can also select whether to explicitly allow or deny this permission to this user or group. This model is similar to the Access Control List (ACL) model that is used by some UNIX variants. Additionally, Windows uses specific permissions to allow users to access folder content. Windows does not use Execute permissions on files. Windows uses the file name extension to determine whether a file (including script files) can be run. The following list describes the basic rules for translating the permissions:
Setting Permissions for a File or FolderTo set the permissions for a file or folder:
REFERENCESFor additional information about securing IIS for migrating from UNIX to Windows, click the article number below
to view the article in the Microsoft Knowledge Base:
324216
(http://support.microsoft.com/kb/324216/EN-US/
)
HOW TO: Secure IIS in a UNIX-to-Windows Migration
| Article Translations
|
Back to the top
