Try mapping the drive with
NET USE, using the
USER parameter. Example:
NET USE Z: \\MyServer\MyFolder /USER: MyServersDomain\MyUserOnMyServersDomain
You should be prompted to provide a password. After a successful drive mapping, you will be able to access the share as
If you get an error about multiple connections with different accounts, try disconnecting all network drives (note: this will also kill any other network share connections you currently have open) and try again.
To disconnect all network drives:
NET USE * /D
If you still can't write to the folder, check the Share permissions on the share. Note that permissions may be split into two parts: "Sharing" and "Security". When accessing the folder locally, only the permissions on the "Security" tab will apply. When accessing it remotely, both "Sharing" and "Security" will apply - the least-permissive of the two will win. So, if you have Full access on "Security", but only Read access on "Sharing", you'll be able to do whatever you want with the folder locally but you'll be restricted to read-only when accessing it remotely.
If you are an Administrator on the server, you can effectively bypass this restriciton by using the built-in administrative shares instead of folder-level shares. For your example local path of
D:\MyFolder you could do this:
NET USE Z: \\MyServer\D$\MyFolder /USER: MyServersDomain\MyUserOnMyServersDomain
In some ways, doing this instead of setting up a share can be better (if everyone who needs remote access to the folder is an Administrator anyway) since you don't have to worry about messing up share permissions and accidentally allowing other people more access than you want them to have.