Windows 2000 Cannot copy file_name: Access is Denied

  • Thread starter Thread starter MadDog
  • Start date Start date
M

MadDog

I have a user that tries copying files into a shared folder and she gets:
"Cannot copy <file_name): Access is Denied. Make sure that the disk is not
full or write-protected and that the file is not currently in
use." I've tried taking ownership, which allows ME to move the files. I give
her ownership and she still can't complete the above task. The disk is not
full or write protected and the user has the appropriate share/ntfs perms.
Any suggestions?
 
Dig deeper into the permissions, look in the "Special" or "Advanced"
Security permissions. If you can do it and she can't then she or her
User Group has a restriction in place.

John

MadDog wrote:

> I have a user that tries copying files into a shared folder and she gets:
> "Cannot copy <file_name): Access is Denied. Make sure that the disk is not
> full or write-protected and that the file is not currently in
> use." I've tried taking ownership, which allows ME to move the files. I give
> her ownership and she still can't complete the above task. The disk is not
> full or write protected and the user has the appropriate share/ntfs perms.
> Any suggestions?
>
>
 
"MadDog" <someone@microsoft.com> wrote in message
news:ePy9jFSsIHA.4952@TK2MSFTNGP05.phx.gbl...
>I have a user that tries copying files into a shared folder and she gets:
>"Cannot copy <file_name): Access is Denied. Make sure that the disk is not
>full or write-protected and that the file is not currently in
> use." I've tried taking ownership, which allows ME to move the files. I
> give her ownership and she still can't complete the above task. The disk
> is not full or write protected and the user has the appropriate share/ntfs
> perms. Any suggestions?
>

You should set the permissions of the "Share" to "Full access
for everyone", then adjust your NTFS permissions to suit your
needs.
 
thanks for the quick replys...i'll look into the suggestions and post back
results.


"Pegasus (MVP)" <I.can@fly.com.oz> wrote in message
news:OOFHzjSsIHA.2064@TK2MSFTNGP05.phx.gbl...
>
> "MadDog" <someone@microsoft.com> wrote in message
> news:ePy9jFSsIHA.4952@TK2MSFTNGP05.phx.gbl...
>>I have a user that tries copying files into a shared folder and she gets:
>>"Cannot copy <file_name): Access is Denied. Make sure that the disk is not
>>full or write-protected and that the file is not currently in
>> use." I've tried taking ownership, which allows ME to move the files. I
>> give her ownership and she still can't complete the above task. The disk
>> is not full or write protected and the user has the appropriate
>> share/ntfs perms. Any suggestions?
>>
>
> You should set the permissions of the "Share" to "Full access
> for everyone", then adjust your NTFS permissions to suit your
> needs.
>
 
"John John (MVP)" <audetweld@nbnet.nb.ca> wrote in message
news:eZPFEZSsIHA.1768@TK2MSFTNGP03.phx.gbl...
> Dig deeper into the permissions, look in the "Special" or "Advanced"
> Security permissions. If you can do it and she can't then she or her User
> Group has a restriction in place.
>
> John
>
> MadDog wrote:
>
>> I have a user that tries copying files into a shared folder and she gets:
>> "Cannot copy <file_name): Access is Denied. Make sure that the disk is
>> not full or write-protected and that the file is not currently in
>> use." I've tried taking ownership, which allows ME to move the files. I
>> give her ownership and she still can't complete the above task. The disk
>> is not full or write protected and the user has the appropriate
>> share/ntfs perms. Any suggestions?
>>
I checked deeper into the permissions as mentioned and did not see any
conflicts (ie group membership perms taking precendence over the user...). I
added this person (temporarily) to the Domain Admins and she was able to
complete her task as normal.

I setup the share as Everyone -- Full Control. I explicitly assigned NTFS
perms on the folder below that. When I stopped inheritance to this folder, I
chose to copy the existing perms and then removed the domain\users group,
added the individuals and gave them the appropriate perms.
 
Back
Top