J
Jon Jones
I have a client with Windows Server 2003 SBS installed. They have a
directory shared that is accessed by both Windows 2000, Windows XP and
Macintosh clients for production files.
The problem they are having is that they cannot change file or folder names.
They can create new ones and change existing data in them, but they cannot
rename them if they try these are the errors they get:
Macintosh - You do not have sufficient access priveleges to rename the item
PC - Error renaming the file or folder. Cannot rename " ": access is denied
I have checked the permission and the security on the share and nothing is
out of whack. They should be able to rename the files and folders. The
last time this happened I removed the share and then reshared the folder.
This allowed them to rename items, but the share has again stopped allowing
them to rename.
I am at a loss as to what is happening. None of the users are making
changes to the security or share settings, unless it is happening by
accident on the mac side.
I am hoping that someone has seen this before and has a solution. Any help
will be greatly appreciated.
directory shared that is accessed by both Windows 2000, Windows XP and
Macintosh clients for production files.
The problem they are having is that they cannot change file or folder names.
They can create new ones and change existing data in them, but they cannot
rename them if they try these are the errors they get:
Macintosh - You do not have sufficient access priveleges to rename the item
PC - Error renaming the file or folder. Cannot rename " ": access is denied
I have checked the permission and the security on the share and nothing is
out of whack. They should be able to rename the files and folders. The
last time this happened I removed the share and then reshared the folder.
This allowed them to rename items, but the share has again stopped allowing
them to rename.
I am at a loss as to what is happening. None of the users are making
changes to the security or share settings, unless it is happening by
accident on the mac side.
I am hoping that someone has seen this before and has a solution. Any help
will be greatly appreciated.