Re: Dynamic volumes on WXPP SP2 make folder and file shares read o
- From: jrb <jrb@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 5 Nov 2005 14:28:03 -0800
Kerry,
Before converting the disks to dynamic volumes, the shares were already in
place and operating perfectly since 2002, when I first bought the machines
(HP xw4100) with WXPP. Access is controlled using ACLs. I moved the folders
with the shares from WNT systems) on DEC Alpha) where the same shares had
been in operation since 1997. (FYI: I have internals knowledge of OpenVMS and
was a security specialist and information integrity consultant for 15 years.
I also have extensive knowledge of Windows.)
The permissions are the same as before the conversion to dynamic volumes.
The permissions allow users of the Administrators and the System groups full
access.
It is NOT the permissions that make the files become read only. Not even a
user in the Administrators group can open e.g. a Word file other than read
only or save a .txt. file after it has been modified. Using Explorer to check
the properties of any file will make it non-delete-able. However, any new
file can be created.
The files become "locked by an other Person or program". It is a lock
problem, as I wrote initially. That is why I have tried to modify lanman
server locks.
When a file has become non-delete-able, it cannot even be deleted directly
on the system holding the share, be it by an Administrator or the owner of
the file.
Only after a reboot can the file be deleted, through any of tools available,
be it over the net (in the share) or directly on the dynamic volume using
Explorer or DOS delete or any other program that can delete files.
Only when a file is created and modified over the net will it become locked.
Files are shared over the local area and are accessible to specific users
only, and to Administrators and System.
Accessing the administrative shares (disk$) as an administrator show the
same looking problem. Files become looked by the process with pid 4 system!
Thanks,
JRB
"Kerry Brown" wrote:
> "jrb" <jrb@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:FDC3EC52-C540-4272-A52F-B31E29652727@xxxxxxxxxxxxxxxx
> > Kerry,
> > Thanks for your response.
> >
> > "Kerry Brown" wrote:
> >
> >> "jrb" <jrb@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> >> news:F3258F53-85D4-4439-AAF4-5BA0764A1659@xxxxxxxxxxxxxxxx
> >> >I have converted the boot disk from basic partition to a simple dynamic
> >> > volume on two workstations running Windows XP Professional with all
> >> > available
> >> > patches (through automatic updates). The reason for this was to enable
> >> > dynamic extensions.
> >> >
> >> > Now folder and file shares served by these machines have become read
> >> > only:
> >> > existing files cannot be updated or deleted. However, new files may be
> >> > created. The new files may again not be updated.
> >> >
> >> > How can this problem be resolved?
> >> >
> >>
> >> Update the NTFS and Share permissions. It sounds like something may have
> >> gone wrong in the conversion process.
> >>
> > I have removed and recreated the permissions. I does not make any
> > difference.
> > The share access rights problem is identical for both systems, although
> > they
> > were done independently of each other. To me, it seems to have to do with
> > the
> > conversion process to dynamic volumes.
> >> > I have tried to modify the LanMan Server (and workstation) parameters
> >> > to
> >> > no
> >> > avail. Disabling opportunistic lock parameters does not seem to make
> >> > any
> >> > difference.
> >> >
> >> > Could it be that dynamic volumes converted from basic partitions
> >> > created
> >> > by
> >> > WXPP SP1 is to blame. I have found that these volumes cannot be
> >> > extended
> >> > as
> >> > they were created by an older version of WXPP.
> >> >
> >>
> >> Boot volumes cannot be extended. It has nothing to do with versions. It
> >> is a
> >> limitation of dynamic volumes that is well documented.
> >>
> >> > Reversing the conversion is not possible.
> >> >
> >>
> >> Yes it is. Delete the volumes, recreate them as basic volumes, then
> >> restore
> >> the data from your backups you created before you started this process
> >> :-)
> >>
> > Well. Right.
> > As the share read-only problem was not noticed until some time after the
> > conversion, a number of email were received after the conversion. In
> > addition, as files were updated to the shares by creating new files with
> > new
> > names and deleting the old, I need to restore backups made from the
> > converted
> > dynamic volumes.
> > Can I restore the ASR backups to basic volumes although they were taken
> > from
> > Dynamic volumes and not loosing any data? Notice, they are systems volume
> > backups, not only data.
>
> I was being facetious. At this point I would leave the volumes as dynamic
> and fix the permissions problem. Check who owns the files, check that
> Creator Owner is listed in the permissions. In the Advanced settings from
> the Security tab click on the effective permissions tab and type in a user
> name that should have full access. What are the results?
>
> Kerry
>
>
>
.
- References:
- Re: Dynamic volumes on WXPP SP2 make folder and file shares read o
- From: Kerry Brown
- Re: Dynamic volumes on WXPP SP2 make folder and file shares read o
- Prev by Date: Re: Home network can not share files
- Next by Date: How to Share a Drive
- Previous by thread: Re: Dynamic volumes on WXPP SP2 make folder and file shares read o
- Next by thread: Re: Dynamic volumes on WXPP SP2 make folder and file shares read o
- Index(es):
Relevant Pages
|
|
