Netware to W2K File sharing issues

From: Michael Mount (mikem@nationalfieldreps.com)
Date: 10/29/02 

From: "Michael Mount" <mikem@nationalfieldreps.com>
Date: Tue, 29 Oct 2002 10:45:29 -0500

Hello,

I've recently moved some files from a Netware 3.2 server to a W2K server as
part of a migration away from Novell. I'm having major problems now with
file sharing and, while I would like to suspect it's unfamiliarity with file
permissions, I can't seem to get around it and was hoping someone could help
me.

The applications we run inhouse use INI style files extensively, often with
shared information amoung users (ie: customization templates, report
templates, etc.). Usually, the INI file does not allow modification by the
user, but some of them do. The application will open the file, read it into
memory, then close it before actually parsing or using the configuration
information. If changes in that file are allowed by the application then
the file will be opened again, the changes will be written, and the file
will be closed. Hence, the files are open for very short periods of time
usually in Read mode.

The problem is that some files are occasionally getting locked and not
released when they are closed. This lock prohibits any other application
from reading the file. The lock can be released by closing the open file
manually or by rebooting the client PC. This was never a problem on Novell
and now has become an ongoing issue with W2K. What we have done to help
minimize the problem is to remove all but Read and Read/Execute permissions
from all non-user modifiable files. Even those still get locked on occasion
but it seems to be less frequently than before.

Assuming that I have the following directory structure and need write access
to FileB.ini and FileE.ini but read only access to all other files except
the DesignDir which would be invisible except for members of the Developers
group. What would be the proper file, directory, and share permissions to
obtain that goal with W2K?

PrimaryShare
 \_ ProductionDir
    \_ FileA.ini
    \_ FileB.ini (RW)
    \_ FileC.ini
    \_ CustomerDir
       \_ FileD.ini
       \_ FileE.ini (RW)
    \_ ConfigDir
       \_ FileF.ini
 \_ DesignDir
    \_ FileG.ini

Or, am I barking up the wrong tree? Maybe there's some other cryptically
worded setting hidden deep in some buried submenu of a subdialog that tells
the OS to release file locks when a file is closed?

Thanks in advance - Mike

Relevant Pages

  • NDS vs NTFS File Scan (F) Capabilities
    ... Novell NetWare administrators can configure permissions so that users cannot ... see files or folders in the file system for which the users do not have Read ... Currently we are in progress of Migrating from Novell 6.0 to Server 2003. ...
    (microsoft.public.windows.server.general)
  • Re: ABE Help
    ... I had to transfer everyone's user folders from a Novell server to the new 2K3 server and now I have to give them exclusive rights to their own user folder. ... I come from teh Novell world and granting access rights aren't this difficult. ... If you've granted "Read and Execute" permission for users on the Users folder, then--by default--those permissions will flow onto the subfolders in the Users folder. ...
    (microsoft.public.windows.server.general)
  • RE: Windows 2003 Server - Everyone Group
    ... this folder only accessable by the users in the "special" group. ... Configure User and Group Access on an Intranet in Windows Server ... NTFS files system permissions control ... group that you want to set permissions for, click Check Names to verify the ...
    (microsoft.public.win2000.networking)
  • Fail DBD::Mysql 4.003 installation
    ... This test requires a running server and write permissions. ... permissions, then retry. ... Failed 9/9 tests, 0.00% okay ...
    (perl.dbi.users)
  • Re: Virtual Directory - Permission Denied with fso CopyFile
    ... TestUser (normal user account with same credentials on all machines). ... I created a share on a remote server. ... reviewing it's sharing permissions and security tab permissions "everyone" ... "directory security" tab on the vdir and selecting, edit, edit and manually ...
    (microsoft.public.inetserver.iis)