Problem
Given the following scenario, I would like to export NFS directories
between two servers, symbolically link the files and share the folders
to be available for access from my Windows clients so that all files
on both servers are accessible to all. The access needs to be
restricted so that UNIX users do not have access to all the files.However, when I set this up, when creating folders or files in the shares causes AFPS 4.0.2 to prevent access to the share yet this works with AFPS 3.5.2n.
A walk through of an example is defined below:
This is an "almost-step-by-step" procedure to reproduce the errors that are seen.
In this example, we use directories instead of filesystems for /disk/0101 etc.
The headings "Filer01:" and "Filer02:" means that the commands have to be performed on that server.
Filer01:
-------
Install a SCO OpenServer 5.0.6 Enterprise System.
Host Name = filer01
Domain Name = sco.com
Standard Security Profile
Lightweight Character Terminal Configuration.
No Optional Software changes.
Install Release Supplement 506a
Install AFPS 4.0.2 as:Primary Domain Controller (PDC) in domain "MATRIX" Remove NetBEUI protocol using netconfig NetBIOS name same as host name. NetBIOS IP address same as TCP/IP address.
Create UNIX group matrix Create UNIX user stt as member of matrix with login group matrix
mkdir -p /disk/0101 /disk/0102 /disk/0201 /disk/0202 Export: /disk/0101 and /disk/0102Using scoadmin->filesystem allowing read-only access from all systems and read-write access from filer02.sco.com
Add root privilege to filer02.sco.com Filer02:
-------
Install a SCO OpenServer 5.0.6 Enterprise System.
Host Name = filer02
Domain Name = sco.com
Standard Security Profile
Lightweight Character Terminal Configuration.
No Optional Software changes.
Install Release Supplement 506a
Install AFPS 4.0.2 as:Backup Domain Controller (BDC) in domain "MATRIX" Remove NetBEUI protocol using netconfig NetBIOS name same as host name. NetBIOS IP address same as TCP/IP address.
Create UNIX group matrixModify /etc/passwd so that user stt will have the same user id as on filer01.
Change group membership and login group for user stt to match filer01.
mkdir -p /disk/0101 /disk/0102 /disk/0201 /disk/0202 Export:
/disk/0201 and /disk/0202using scoadmin->filesystem allowing read-only access from all systems and read-write access from filer01.sco.com
Add root privilege to filer01.sco.com Filer01:
-------
Mount filer02.sco.com:/disk/0201 in /disk/0201 and filer02.sco.com:/disk/0202 in /disk/0202 using scoadmin->filesystem, using default settings. Filer02:
-------
Mount filer01.sco.com:/disk/0101 in /disk/0101 and filer01.sco.com:/disk/0102 in /disk/0102 using scoadmin->filesystem, using default settings. Filer01:
-------
mkdir -p /disk/0101/pro0101/doc /disk/0102/pro0102/doc Filer02:
-------
mkdir -p /disk/0201/pro0201/doc /disk/0202/pro0202/doc Filer01:
-------
mkdir /pro ln -s /disk/0101/pro0101 /pro ln -s /disk/0102/pro0102 /pro ln -s /disk/0201/pro0201 /pro ln -s /disk/0202/pro0202 /pro net share pro=c:/pro /remark:"Filer01 Pro Share" net perms c:/pro /grant "Domain Users":change Filer02:
-------
mkdir /pro ln -s /disk/0101/pro0101 /pro ln -s /disk/0102/pro0102 /pro ln -s /disk/0201/pro0201 /pro ln -s /disk/0202/pro0202 /pro net share pro=c:/pro /remark:"Filer02 Pro Share" net perms c:/pro /grant "Domain Users":change chmod -R 770 /disk/* chgrp -R matrix /disk/* Filer01:
-------
Change registry settings in AFPS:
IgnoreUnixPermissions = 1
UnixGroups = 1
mapuname -a "MATRIX:Domain Users" matrix
(The only AFPS group that AFPS user stt is a member of) Filer02:
-------
Change registry settings in AFPS:
IgnoreUnixPermissions = 1
UnixGroups = 1
mapuname -a "MATRIX:Domain Users" matrix
(The only AFPS group that AFPS user stt is a member of) Client01:
--------
Log on to a Windows workstation as user stt.
(have seen these problems on Win98SE, WinNT4, Win2k)
Map network drive P: to \\filer01\pro
Map network drive K: to \\filer02\proCopy c:\autoexec.bat to P:\pro0101\autoexec.bat [PASS] (unix user, group and perms set correctly)
Copy c:\autoexec.bat to P:\pro0201\autoexec.bat [FAIL] (unix perms not 777)
Create new folder P:\pro0101\src [PASS] (unix user, group and perms set correctly) (however, unable to browse this newly created folder from K:)
(This next step causes loss of all access to the share) Create new folder P:\pro0201\src [FAIL] (Cannot create file when file already exists)
Change directory to any directory on P: after the above command [FAIL] (Folder was moved or removed)
This "failed state" lasts for some time, or until the SERVER service has been restarted.
Solution
This problem has been reported to SCO Engineering and as a work around it is recommended not to use symbolic links over NFS shares with AFPS.
See also
ta100067, "SCO Advanced File and Print Server permissions."
ta100046, "Group permissions are not recognized on an NFS exported AFPS share."