Mac Yosemite writing files to Windows 7

I just bought a MAC Book Pro to learn the Mac OS X.  I am starting to see a lot come into business now:  

I am converting video files into Mpeg4 format.

I can connect and copy files from windows 7 SP1, 64, 32 Gig of RAM to Yosemite Mac, but I can not copy back to the Windows7 Machine.  When I try to copy back I get a very non descriptive error, "The operations can't be completed because you don't have permissions to access some of the Items."   I can create a test folder when connected from the Mac to the Windows 7 machine.

Seems to be saying that I did not set permissions up correctly.  However, I can connect with the Mac to my windows 2008R2 Server to a test share with my user ID authenticate to it from the Mac and the file copies to the NTFS share there no issue, a little slow but copies.  I can authenticate from the Mac to my Windows 2012R2 file server, and copy the files over to the NTFS share no issue, and these Shares are NTFS in both cases. Yosemite uses SMB 3.0 Confirmed with Mac tier2 support.

I have a work around after the file is done ripping copy to the 2012R2 file server - Connect with the Windows 7 Machine and copy to the DVR system.  this is the log way around the block would like to fix for me and others who are having the issue.  I think SMB is the issue.  I have SMB2 enable, but I can't find a place to upgrade to SMB 3.0 for Windows 7.
RickArnoldAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

David Johnson, CD, MVPOwnerCommented:
check the share permissions on the windows 7 machine a standard share when setup only allows reads and not writes.
arnoldCommented:
To David's point, there are two sets of permissions,
One is the share permission, write permissions need to be granted here
Page other is on the security tab unless you are uising simple sharing, the user with whose credentials you are accessing the share has to have write rights.

It also depends on the type of share.  You can add to windows tools for Unix that will allow you access to shares using NFS share versus smb share which presumably you are now using.
RickArnoldAuthor Commented:
The Permissions I believe are set correctly.  I can write a test folder in the share from the Mac side.  If the permissions were set incorrectly, I would not be able to authenticate or Write the folder see screen shots. This is the way I have it setup.  

Thanks for the help,
Rick
Security.PNG
Sharing.PNG
Acronis True Image 2019 just released!

Create a reliable backup. Make sure you always have dependable copies of your data so you can restore your entire system or individual files.

arnoldCommented:
Folders are different from files.  Mac files are of two parts. A resource fork and a data portion.

In windows features add Mac related options for file sharing.
arnoldCommented:
Are you able to copy an existing file while unable to create the file directly the share? Or you run into issues with both?
RickArnoldAuthor Commented:
arnold, (good name),  

I can not copy an mpeg4 file to windows 7 from the Mac, the result of the rip.  From Windows 7 I can copy the Mpeg file for  ripping to the Mac.

See the rest of what I can connect to below:

However, I can connect with the Mac to my windows 2008R2 Server to a test share with my user ID authenticate to it from the Mac and the file copies to the NTFS share there no issue, a little slow but copies.  I can authenticate from the Mac to my Windows 2012R2 file server, and copy the files over to the NTFS share no issue, and these Shares are NTFS in both cases. Yosemite uses SMB 3.0 Confirmed with Mac tier2 support.

Thanks very much this is my first foray into Mac

Rick
arnoldCommented:
Can you copy any file into the windows 7 share? Of any size any type? Or the issue comes up based on the size.....
Try checking the advanced firewall setting on the windows 7 dealing with which smb, smbv2 allowed through the windows firewall if active...

One other though does your windows 7 have an anti-virus application which could explain it.

Try copying a file from the windows server to that share.


Are you copying or moving the file?
RickArnoldAuthor Commented:
I did a lot of testing.  This is what is going on:

The files will convert to the .mp4,  and I can Rip a DVD in the MAC to mp4.

When I try to copy the file to windows, I get permission errors.  If I do a command I and take off the file extension in my file folder the program sets, it will delete the file and I have to re-rip.  

If I copy the file to the desktop of the MAC and then do a command I on the desktop file remove the extension and can then copy to windows directory with no problems, and I put the extension back on. I get no permission errors.  If it were truly a permissions issue,  I would not be able to copy the file in any case.  

I go back back to the MAC and delete the files and I am ready to go again.  Very strange behavior.

Rick
RickArnoldAuthor Commented:
I don't get this with any other file type

very weird
serialbandCommented:
Is it possible that your file name and path is too long?  Yosemite now erroneously gives permissions errors for path length errors.  Older OS X allowed you to exceed the Windows path length limitation, but that appears to no longer be possible in Yosemite.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
RickArnoldAuthor Commented:
That is what I am experiencing and it does not appear with any other file, and perhaps it is due to file name length.  The other files that I tried has shorter names.  

But, interestingly enough  if I take the same files and save it to my windows 2012R2 server I can keep the extension and I get no weird errors.  My initial thought is had something to do with SMB protocol.  In windows 2012R2 MS made improvements in it and it is faster.  I can tell the  file copies down much quicker and I don't get the weird permission issue.

Thanks,

Rick
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Mac OS X

From novice to tech pro — start learning today.