OSX leopard Server 10.5.8 SMB sharing problems with Windows XP machines

I think your problem is in the SMB permissions. Even though you've set an ACL permission of RW for the user, the setting you applied in the SMB protocol options for where only the Owner has RW permission is messing it up. Change that to "Inherit permission from parent", save and propagate the permissions to the share point.

The ACL should not be able to override the permission setting of the protocol used.

-Douggo

Hi,

I have exactly the same problem, I use a mac server leopard 10.5.8 in a multi envirronement with mac clients and windows XP, 2003, Seven and when downloading files for the internet and storing to SMB share of Leopard server no problem,but after that I can't write back files to any kind of windows ! On XP and 2003 it give me the same message than describe the file seems to copy but at the end it fail to save on windows 7 it say that Group Sector are not valid ! Strange, same problem on all windows versions.

I have try with Mac clients no problem ! What could help is that it seems that only new files have problem to write back. I have file on the MAC Server that are set in 2008 and thoses files can be write back to windows.

I have test to copy some files I have on my windows clients some .txt or .exeand copy back with no problem ! But as soon as I download files from the web, if I copy theses files to de server they can't be copied back to windows, I can open or delete the file,if it is a zip file i can extract to the windows clients but impossible to copy the file back to windows computer !

No that I don't know if it is the same problem but moste of my office excel files can't be correctly written, most of the time Excel 2007 crash the file and Excel 2003 make a copy of the file at every save i made, something goes wrong but I don'tknow how to troubleshoutthat, of course no problem in same situation with a smb share on a windows server !

Have you an idea ?

Thanks Rgds ?

As per my advice to the OP, I would look at the Permissions properties in the SMB Protocol options first. The root of the share point should have the least restrictive permissions. My experience has been to use the "inherit permissions from parent" option at the share root; I can crank down the restrictions using ACL's for the subdirectories. (Also, when dealing with SMB, I do employ oplocks to prevent multiple users opening the same file.)

Once you have to SMB protocol permissions set, propagate the permissions to the share point. Then go to the subdirectories and set any User/Group ACL's you might need to employ, propagating the permissions for each directory as needed.

I have file on the MAC Server that are set in 2008 and thoses files can be write back to windows.

Are you referring to a file that originated in the year 2008 or a file from Office 2008??

-Douggo

Dear Douggo,

thanks for your help I have found something just now I must investigate: I have one Windows XP SP3 where all works fine, I just receive a message about :AFP_AFPINFO:$DATA and :AFP_RESOURCE:$DATA that can loose some data i accept and the file can come back to windows xp, an other windows xp sp3 with the same file give me the error like on all win2003 clients !

Over my prévious mail:

When I download new files form internet, as soon as I copy thoses files to the Mac OS X Server, I am uanble to return back to windows, open or delete ok but copy refused !

On the server leopard, I have a lot of files and it seems that the old oneform 2008 can be copied back to windows but new one are unable to copy back to windows. All the files in the directory was downloaded form internet at a moment.

if I take a file executable form my windows 7 program files directory and I put it on the server leopard, then I can copy back to windows I have try different files form different directory without any problem!

So my conclusion is that only files downloaded form internet now are in problem and maybe because they write something different in AFPINFO and AFP RESSOURCE that can cause problem for some windows version or configuration.

I hope that could help us 🙂

have a nice day.

Fabrice.

I would still suggest investigating the Permissions settings in Server Admin for the directory housing the files. The fact that you can write and open (execute) files on the server but not copy (read) suggests that there are custom permissions set in the User or Group ACL's assigned to the directory.

The :AFP_AFPINFO:$DATA and :AFP_RESOURCE:$DATA are how the Windows NTFS file system "sees" files on an Apple HFS volume. Samba should keep those hidden and deal with them properly.

-Douggo

Dear Douggo,

Thanks for your help but I think you are on the wrong way with permissions,I have already check permissions, all POSIX permissions are full access every one,and the ACL are also all rights to every ones, I have first remove allmy old permissions since I also think that the problem was there but without success.

And like I try to explain before the problem are not dependant on user but on operating system and updates or config of thoses OS.

To resume the problem occure for some WINXP, all WIN7, all WIN2K3 for all files in the same directory that have been downloaded by internet recently old files and files that are copied from other computers on the network and that are not from the internet seems to not be concerned by the problem ! Yes it is very strange. All mac os clients works fine !

And finally the error message are different from WINXP than WIN7 than WIN2K3 but for WINXP where the copy back are functionnal, I receive a message that ask me if I want to copy files even if some information are loose (AFP_AFPINFO and AFP_RESSOURCE).

I would to know more inforation about cross platform informationabout the meta-data AFP_INFO etc...

If you have other suggestion let me know 🙂

Thanks for your help.

Okay, lets put permissions aside for the moment. 🙂

You have an NAS box on your network, from which you then create and share out directories from OS X Server to your PC and Mac clients, right?

What happens if you use a share point that is local to the server rather than one on the NAS box?

The :AFP_AFPINFO:$DATA and :AFP_RESOURCE:$DATA information are the resource forks of a Macintosh-created file. Windows servers without Services for Macintosh should split/strip those forks out when copying to an NTFS volume.

Alternate data streams allow more than one data stream to be associated with a filename, using the filename format "filename:streamname" (e.g., "text.txt:extrastream"). Alternate streams are not listed in Windows Explorer, and their size is not included in the file's size. Only the main stream of a file is preserved when it is copied to a network share or FAT-formatted USB drive, attached to an e-mail, or uploaded to a website. As a result, using alternate streams for critical data may cause problems. NTFS Streams were introduced in Windows NT 3.1, to enable Services for Macintosh (SFM) to store Macintosh resource forks. Although current versions of Windows Server no longer include SFM, third-party Apple Filing Protocol (AFP) products (such as Group Logic's ExtremeZ-IP) still use this feature of the file system.

-Douggo

Dear Douggo,

Not exactly 🙂

I have a MAC PRO with MAC OS X Leopard 10.5.8 (not yet upgraded to 10.6.1,on order) on this server are all my company datas on smb share (I Have a Apple Raid with 4x 1Tb HDD) since I workin the company with mac clients and windows clients,in fact everybody are in windows clients XP, 2K3 and Win7 and I am alone in Apple client, with iMac and a Mac Mini.

The data server are so my MAC PRO with MAC OS X leopard server and it share files over SMB protocol, I don't have NAS. I have different share with different permission, the problem exist on all share, so I have a share were I store mainly internet files (no critical for company) and I have remove all permission and place everyone fullcontrol to troubbleshout but right now without success.

When you access form Windows 2K8 or Windows 7 to the smb share of MAC OS X Server and you try to copy files from the share to the desktop of theses PC clients the file start to copy, you wait till near the end and when the end are reach, you receive a message saying the the source of copy are in trouble and that the file can't be copied. During all the time the file are in copy process, you have a new file created on the desktop of the client at the name of the file you copy, as soon as the copy give the error message the file are remove !

For some windows XP pro sp3 clients the copy works and at the end in place or the error message I receive an other message saying that the AFP RESSOURCES can't be copied and asking me if I am ok with that, I say no problem and I have the file on the desktop. For those xp where that doesn't work, it is the same as on 2K3 clients.

What's strange is that the problem seems to be file dependant,like explain before, I constat that only recent file downloaded from internet are affected by that,and I don't see any different in permission nor in ACL neither in POSIX !

What I need is may be a service on the mac os x server named :'Services for Windows' 😉

Hope you can help.

Have a nice day.

Dear Douggo,

I have find something interresting !!!!!!

Why that works on some Win XP and why not on others 🙂 Because someare with FAT32 and others with NTFS !!!

If you copy files from MAC OS X to a PC clients FAT32 partition it isok you just receive a message saying that you can loose AFP Forks.

But if it is an NTFS partition then it start coping and hang at end with errror 🙂

NOW how to find a solution since I don't want to return to FAT32 inplace of NTFS 🙂

Wel I have just make a new test:

Form the MAC OS X Server 10.5.8 I copy to an SMB Share of my iMAC with 10.6.1 a file that cause problem when copied toan NTFS client drive. And stangly when I try from the windows PC to copy exactly same file from the smb share of 10.6.1 it copy back to ntfs without problem !

I am not sure that it would indicate that something are corrected in Snow Leopard, but these test should may be help to understand.

May be the problem come from MacFuse 2.0.3 installed on mac os x server, but it is also installed on imAc 10.6.1 🙂

What could i do more for testing the reason of problem, have you an idea ?

Thanks.

FAT32 or NTFS should not make a difference on the client side when you are copying a file residing ON the server FROM the client (Win2K, XP, Win8). I would not push files residing on the server over peer-to-peer connections (client-to-client).

I also would not be running MacFUSE on a server just to avoid problems unless I really needed the ability to write to NTFS volumes for some reason (and I can't think of many reasons that I would want/need to do that).

If you have something like a USB flash or hard drive that you could connect to the server and create a share point on, I'd be interested seeing if that works. Perhaps an issue reading files from your RAID on the Windows clients?

-Douggo

Dear Douggo,

I don't know really what I have change (I have an idea) but now that's working :-)no more crash when copy back.

Here the CHANGE:

1) Upgrade from Leopard 10,5,8 to SL 10,6,2
2) Connect my SL to Active Directory (Member Only) (I suppose this it the big change)

So now I have no more copy problem !

BUT I have a new serious problem with SNOW LEOPARD SERVER, all the SMB SHARE are very slow for Windows Clients but mainly only slow to connect to the share after that that's working pretty good for a moment till the timeout of the connection ! I am searching the web for a solution my company restart on monday and I have big fear that most of my users complain with the speed for connecting to SL SMB share ! I receive some Opendirectory fail to read DomainAdmin in smbd.log but I open anew threat to avoid poluate this one !Thanks for your help.

Felee

Felee,

I receive some Opendirectory fail to read DomainAdmin in smbd.log but I open anew thread to avoid poluate this one

Yes, I would have suggested opening a new topic in the Snow Leopard Server forum for advice on that issue. I'm still on plain Leopard Server and wouldn't be able to offer insight on your new issue.

Glad that you got it resolved, at least partially.

-Douggo

Hi!

Do I get it correctly: you store a file on a SMB share but then cannot copy it back to your Windows PC local drive?

I have seen similar thing on my 10.5.8 Server and the reason was that the file was blocked. You can open the Properties sheet for the file and click the Unblock button. This will remove a special NTFS alternative data stream called Zone.Identifier from the file and then you can freely open the file. OS X file system also supports alternative data streams or forks, so this also applies to OS X Server shares.

This webpage was one of the first I found at the moment that sheds some light on the issue.

http://community.tigranetworks.co.uk/blogs/tim_long/archive/2009/03/30/how-windo ws-tracks-a-file-s-security-zone.aspx