#Share vs ntfs permissions full#

Of course in realistic environments, permissions can become more complex. Permissions are applied to the Authenticated Users group at the SHARE level and NTFS permissions are applied to John Smith directly. In this example, John Smith is the Authenticated Users group. Here is a simple example to help you better understand how SHARE and NTFS permissions impact the user accessing the resource. Whatever permissions you set in the Access Control List (ACL) will take effect since the NTFS permission will be equal to or more restrictive than the permissions defined in the SHARE tab. The most RESTRICTIVEВ permission is the effective permission.ДЄs a general rule, it is an acceptable practice to set the SHARE permissions to вЂњAuthenticated Users/Full ControlвЂќ and manage the permissions via the NTFS Security tab. If you are accessing a resource (file, folder, etcвЂ¦) over the network, then you combine the SHARE and NTFS permissions. In a scenario where the user is logged on locally, only the NTFS permissions are evaluated. If you are logged on a computer locally, the SHARE permissions applied to a folder have NOВ impact on the user. When both permissions are in place, the most restrictiveВ permission will be applied to the user accessing the resource. NTFS permissions determine the action users can take for a file or folder when accessed locally.

There are three types of share permissions: Full Control, Change, and Read. SHARE permissions are not evaluated when users are logged into the resource locally.

The SHARE permissions determine the type of access users have to the shared folder when the resource is being accessed over the network. SHARE permissions are not applied to files. SHARE permissions are the permissions you set for a folder when you share that folder. The concept of SHARE vs NTFS permissions has confused many IT professionals over the years.

#Share vs ntfs permissions full#