If necessary, use the MS-DOS attrib or the OS/2 chmod command to change the file attributes. You also can use the Properties menu in Windows Explorer.
If you can communicate with the server but cannot access a shared resource, check the following items:
1. Verify that the shared resource exists by using the net view \\servername command. If the shared resource name is not displayed, then it does not exist. In that event, you must re-share the resource.
2. Link to the shared resource while logged in as administrator. If this fails and the resource exists, then the resource may be shared incorrectly. Delete and re-share the resource. If this succeeds, then proceed to the next step.
3. If the resource is a disk resource, check both levels of permissions associated with the shared resource. First check the share permissions using Server Manager. Then check the permissions on the shared directory using Windows Explorer at an administrative client.
Verify that the resource can be used using either group membership or on a per-account basis for that particular user. Also, verify that the access permissions on the resource allow the desired action to be performed (for example, the user has read-only permission but is attempting to edit a file). Also verify that the maximum user limit for a particular shared resource is not being exceeded.
4. On the shared resource, check the file attributes and the UNIX system access permissions.
If necessary, use the MS-DOS attrib or the OS/2 chmod command to change the file attributes. You also can use the Properties menu in Windows Explorer.
This section describes the differences between the access permissions of the UNIX system and a network running Advanced Server software. It explains the UNIX system access permissions — how to display them and how to change them with the uchmod command. The uchmod command is available as both MS-DOS and OS/2 executable command and resides in the DOSUTIL and OS2UTIL shared directories.
An Advanced Server is a computer that also is running the UNIX operating system. All of its files also are UNIX system files with their own set of UNIX system access permissions.
UNIX system access permissions on an Advanced Server file will be compatible with the Advanced Server only if the UNIX system access permissions are changed explicitly. If these UNIX system access permissions are modified, they can prevent access to a file or directory even if Advanced Server access permissions grant access.
For example, if a user has Advanced Server change permission for a file, then this file needs to have the UNIX system equivalent of change permission (RWX) in order for the user to perform all of the operations allowed by the Advanced Server change permission (read, write, create, and execute).
However, if you changed the file’s UNIX system permissions, eliminating the write (W) permission for everyone other than the file’s owner, then no one but the owner can alter or remove the file, regardless of the generous Advanced Server permissions.
Advanced Server automatically adds the appropriate UNIX system access permissions when files and directories are created on the network. These permissions are determined by two keywords in the Advanced Server Registry: UnixFilePerms and UnixDirectoryPerms.
Check whether the values assigned to these keywords provide the desired UNIX system protection for your files and directories. These keywords are in the following key:
\SYSTEM\CurrentControlSet\Services\AdvancedServer\FileServiceParameters
For more information, see Appendix A, "Advanced Server Registry."
For more information about security and access permissions, see Advanced Server Concepts and Planning.
