4
I have a RoboCopy problem and here is the scenario.
My server is running Windows Server Essentials 2012 R2. My laptop is running Windows 10 Technical Preview. The server is running as a domain controller but my computer is not joined to that domain.
I have a share on the server called "Pictures", so it's located at ~ \\192.168.1.10\Pictures
which I have mapped as P:
using an account tha thas Full Control privileges on that folder. I've been trying to mirror that folder to my local machine using the simple command:
RoboCopy P:\ "C:\Users\[MyUsername]\Pictures" /MIR
This always returns the error ERROR 5 (0x00000005) Accessing Destination Directory
even though the destination directory is under my user account where I am the owner. I have tried using both an administrative command prompt as well as the standard user command prompt. Neither works :(
Using RoboCopy between two local folders using the Pictures folder as a destination works just fine, so I'm guessing this has something to do with domain permissions rather than the actual destination permissions.
P.S.
The funny thing is this worked just fine when my computer was using Windows 8 and connected to the Server Essentials using the Connector application without domain joining (The Connector app isn't available for Windows 10).
P.P.S
Copying directly in Windows Explorer works just fine, but I need RoboCopy since it's much more efficient at syncing large folders.
Any help would be appreciated.
Update
I am unable to try with a local user on the server since the server is a domain controller. I did however try to give the domain user I use to map the network drive on the workgroup machine full permissions on the folder as well as making him owner and still no dice. Here is the exact RoboCopy output:
------------------------------------------------------------------------------- ROBOCOPY :: Robust File Copy for Windows ------------------------------------------------------------------------------- Started : fimmtudagur, 25. júní 2015 21:40:01 Source : P:\ Dest : C:\Users\stefa\OneDrive\Pictures\ Files : *.* Options : *.* /V /S /DCOPY:DA /COPY:DAT /R:1000000 /W:30 ------------------------------------------------------------------------------ 25 P:\ 2015/06/25 21:40:02 ERROR 67 (0x00000043) Accessing Destination Directory C:\Users\stefa\OneDrive\Pictures\ The network name cannot be found. Waiting 30 seconds...
Update 2
I'm fairly certain I have just hit a bug in Windows 10 (still there in 10159). When I try this on a Windows 8.1 machine (x64 as well as RT, clean install on both) by using robocopy over a mapped network drive or net use \\192.168.1.10\IPC$ ...
everything works just fine. But using a Windows 10 client, this does not work. My theory is that either something is has broken in the way Robocopy does network copies in Windows 10 or something in the network stack in Windows 10 has broken RoboCopy.
Can you run Robocopy with elevated privileges just to see if that helps – Dave – 2015-06-25T11:28:19.257
Already tried that. Same error. Only difference is that I have to map the ndrive manually using net use when running elevated since that can't access the user mapped drives, but it results in the same error message. – Stefán Jökull Sigurðarson – 2015-06-25T11:42:29.057
I assume the robocopy is being run as a workgroup (eg local) user? Is the drive mapped using a domain user account? Have you considered creating a local account on the server you can use for operations where the client is not in the domain? then you could map the drive and run the robocopy under the same account. – Frank Thomas – 2015-06-25T13:04:15.190
1Also have you tried using the literal UNC path to the share rather than the mapped drive? – Frank Thomas – 2015-06-25T13:06:51.827
@FrankThomas: Yes, RoboCopy is running as my local user on my computer (Microsoft Account). I haven't thought of creating a local user on the server and trying that. I'll do that once I get home (I'm at work currently).
I have tried mapping the UNC literal path, that did not work either. – Stefán Jökull Sigurðarson – 2015-06-25T13:45:19.903
@FrankThomas I updated the question with more information. – Stefán Jökull Sigurðarson – 2015-06-25T22:01:54.347
hmm. That particular error is somewhat unexpected. the user running the job should have no trouble locating or writing to the local path. you said you took ownership of the folder as the domain user. does it still allow your Microsoft Account full control? be sure to propagate any permissions changes to all child objects. Also perhaps try this approach, by unmapping your network drive, and putting the connection inside a batch file with your robocopy command. http://sergeit.blogspot.com/2014/05/sync-network-folders-to-onedrive.html Bonus, you can use
– Frank Thomas – 2015-06-25T23:23:44.543MON=1
to sync continuously.Let us continue this discussion in chat.
– Stefán Jökull Sigurðarson – 2015-06-26T00:08:54.927