Can't save to SBS 2003 (but I used to be able to)

Discussion in 'Windows, Linux & Others on the Mac' started by durija, Aug 14, 2008.

  1. durija macrumors 6502

    Jan 16, 2008
    A small network with the file server/domain controller running MS Small Business Server 2003. The Macs could not talk to it at all when we installed the system 3 years ago. So on this server we installed an app from Group Logic called ExtremeZ-IP. This allows for administration of sharing for the Macs and apparently lets them understand NTFS, long file names, whatever.

    Life was good until we installed the Service Pack 2 on this server. Now, everything is exactly the same with one exception. We cannot save a file to any of the shares on the server. We can move, copy, paste, read, manipulate, do anything but save. Anybody experience anything similar after upgrading to SP2?

    By the way, upgrading to the most recent version of ExtremeZ-IP MIGHT fix this. But I don't want to pay over $1000 without knowing (pricey, yes?), especially when there might be a simple fix.
  2. charles-kim macrumors newbie

    Aug 14, 2008
    ExtremeZ-IP Support

    Sounds like a strange issue, but I'm sure there is a simple solution.

    ExtremeZ-IP and NTFS permissions
    - SYSTEM account should have full control across the drive
    - We ignore permissions set under the sharing tab, and only enforce permissions as reflected under the Security Tab
    - If you find some user’s permissions are not being enforced as expected, from Windows go to the Security Tab > Advanced > Effective Permissions and check what Windows is reporting.

    You can try re-propagating permissions.
    If the problem isn't related to permissions, try creating a new ExtremeZ-IP Volume "C:\Test" and see if you can reproduce the problem. If not then the problem is probably volume specific and the following approach should fix this type of condition.

    Break "Studio" share within Windows and delete Volume within EZIP
    Next, rename the folder on Windows: D:\Studio to D:\Studio_old
    Next, create new folder: D:\Studio
    Next, drag contents from D:\Studio_old to D:\Studio

    Drag groups of folders vs. all at once
    Avoid copying trash cans, .Temp folders and such
    If something fails to move then copy around this problem area

    Next, Recreate D:\Studio share within Windows and EZIP

    The drive root (D:\) and newly created folder being shared out (Studio) should both have SYSTEM=Full Control

    The folder migration should take about the same amount of time that pushing permissions take, as the files don’t actually get moved. This will fix file ID problems and when the newly created folders are re-shared, new mapping streams will be created.

    There are lots reasons to stay current on the latest version.
    Leopard clients will definitely have problems on any versions prior to 5.2.1 (we are currently at 5.2.2x10).

    A complete list of changes can be found:

    Best Regards,
    Charles Kim
    ExtremeZ-IP Support
  3. durija thread starter macrumors 6502

    Jan 16, 2008
    Thanks for the response Charles. I'm sending your suggestions to our IT guy. I know he's tried some of them, but maybe not all.
  4. charles-kim macrumors newbie

    Aug 14, 2008
    Leopard Finder Changes

    You are welcome.
    Apple made some changes to the finder in 10.5, so if you are running Leopard against an old version of ExtremeZ-IP you won't find browsing via the finder reliable.

    In a folder where 100 items show up on the server, Leopard may only see 10 or worse zero until the remount the share. This will end up being a common issue and one which is likely to cause great confusion.

    So even though the issue you report probably isn't related, you should still upgrade.

  5. durija thread starter macrumors 6502

    Jan 16, 2008
    We are still running Tiger here (Leopard at home only) and are likely to be doing so for quite a while due to the need to access several legacy devices. I have found references to this problem scattered across the web, but no exact matches or sure fixes. I think it is definitely a Server 2003 issue. If I was sure EZ-IP wouild fix the problem, I would probably recommend the upgrade. But at this point I am not so sure that wouild do the trick.

Share This Page