Can’t copy files on windows

network-sharewindows 10

I've a client, for which I've instantiated a shared folder on Windows 10, I showed him how to manage permissions etc.. The problem is that I'm going to make hardware changes, and I want to copy the data to another driver. When I try to copy some files I get you this error:

"You need permissions from admin to make changes to ****" - or something similar

The problem is that I'm admin. The first thing I've tried is taking ownership of the files, this didn't work. The second thing I tried is running file explorer as administrator, this didn't work also. The admin account has all permissions allowed and none denied. Any ideas what may be wrong?
Edit
here is what I get from the command line:
1. Navigate to the share

E:

after that I'm using "cd" to get to the directory containing the file, them

E:\Folder1\Folder2\Folder3>copy "FileName.max" "F:\Folder1\Folder2\Folder3\FileName.max"
Access is denied.
        0 file(s) copied.

I'm running cmd as administartor
Note that I've changed the names of the directories and the file name for privacy reasons.

Best Answer

Try to use procmon tool from SysInternals Suite, while you trying to copy this file. This should give you hint what permissions are required to copy this file.

Related Solutions

Windows Server 2008 – Following Windows SymLinks in Network Shares

The target of the Symlink needs to be able to be accessible by readers. In your case...

E:\
|- Folder1\
|- [share]Folder2\
      |- slF1

If 'slF1' points to "E:\Folder1\" clients will not be able to access it. In fact, if you'd done this:

E:\
|- Folder1\
|- [share]Folder2\
      |- Folder3\
      |- slF3

And made "slF3" a link to "E:\Folder1\Folder3" it STILL wouldn't work since Clients don't know how to access "E:\". However if you had made "slF3" a link to "\\Server\Share\Folder3" it would work just fine. To make it work the way you want it to work:

E:\
|- [F1Share]Folder1\
|- [F2share]Folder2\
      |- slF1

Made "slF1" a link to \\server\F1Share\ and it should work just like you need to.

mklink /D slF1 \\Server\F1Share\

The thing to keep in mind is that a symbolic link is a path that is followed explicitly by clients, as if it were a Shortcut icon. What you link to will be what clients attempt to attach to. Shares do not derefence links before serving them up, clients have to support them. That might be a problem with older clients that can't handle junctions.

The reason sharing it directly works is because Windows is actually sharing E:\Folder1 in that instance, and the symlink is never touched by clients.

Can you set CIFS permisions from EMC Command Line

No, you cannot modify the permissions of a share from the Control Station or from the Celerra Management interface. (This may seem like a dumb thing, but for those of us that ONLY manage the storage it's a boon!)

When you create a share, it should initially come up with Everyone/Everyone permissions. Are you sure you're a full domain admin? I've run into issues where my "Domain Admin" account wasn't actually in the Domain Admins group and I was not able to set permissions.

Related Topic