nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Mac permission issue

DaveDeutsch

We're running TS 6.7.2 (no SPs) on Windows 2003 R2. Our Macs are running OS 10.7.4. When we try to access Teamsite files over the Teamsite share (\iwserver) from a Mac, the permissions appear "read only". When the same files are viewed over the same share from Windows, the permissions appear "read-write". Teamsite is configured to use AD security as are the Macs (same security domain).

1) Any ideas why this is and how to resolve? I've tried keyword searches on this forum for "network share" and "mac" but didn't get any relevant hits.

2) Does anyone have success using this same configuration in their environment - success meaning file permissions are consistent?

3) For those on TS 7.x, are you having good experiences integrating with Macs on OS 10.7.4 over the \iwserver mount?

To add a layer of mystery to this, from a Mac over \iwserver a user can create a new file but cannot delete it because they lack "write" permission. Odd.

Thanks in advance!

Find more posts tagged with

Comments

Rick Poulin

I'm not sure where to start helping you troubleshoot this.. What I *can* say is that I do all of my development on mac and have never run into this problem, back to using OSX 10.4 on TS6.5. At present, I'm working with 10.6.7 against TS 7.2 on Win2k8 R2 x64. Both /iwserver and /y$ work just fine over SMB.

Do you perhaps have other (dev/test/qa) servers you can try?

Top10MPM_TEST_DB.rptdesign

MpM_Chart_Drill.rptdesign

DaveDeutsch

Thank you for that feedback. Unfortunately this is the only Teamsite server in our environment.

As a place to start I'm focussing on the security handoff between the SMB network share and the TeamSite shared drive. Based on our tests the evidence suggests there are different layers of security involved. The Mac appears to be authenticating on the shared drive against Windows security whereas on a Windows machine it appears to be authenticating against whatever Teamsite layer of security exists. The former doesn't work, the latter does. I'm not intimately knowledgeable on such things but am engaging those who know more.

In your Mac environment, do the Mac users authenticate against AD? In particular, is it the same AD that Teamsite users authenticate against provided you have Teamsite configured that way?

Thanks in advance!

Snap 2016-10-26 at 10.48.37.png

Rick Poulin

In your Mac environment, do the Mac users authenticate against AD? In particular, is it the same AD that Teamsite users authenticate against provided you have Teamsite configured that way?

Yes, that's the case. Note, however, that we don't automatically join a domain. When I access a network share on any TS server, I'm always prompted for a u/p, at which point I use my AD creds (the same ones I use to authenticate in TS's web UI).

Based on your analysis, this might not make any difference.. but does it work any better if you connect to /y$ instead of /iwserver? I know that's not a best practice, but it might help you point the finger at whatever magic makes the "/iwserver" nonstandard-share happen.

DaveDeutsch

At our company the Y drive is the corporate shared drive, therefore I configured the T drive to act as the mount point for \iwserver. The T drive defined on the Teamsite server itself is not shared out, therefore when I had my Mac users test it they could not connect to it (as expected). They can connect to \\\iwserver however.

I will talk to our Active Direcory/Windows teams to help figure out if manually logging into the share will make a difference. At least I'd know AD credentials were being used.

DaveDeutsch

I should add we are using Teamsite groups, not AD groups, to control group access in Teamsite.

ChartDrillDown.rptdesign

ChartDrillDown2.rptdesign

Rick Poulin

Well, Y or T shouldn't make a difference here.. (and I pretty much always use TS groups).

Whether you explicitly share the T drive doesn't matter. All drives are always implicitly shared via the hidden \\server\x$ path (where x=drive letter), but only users in the Administrators group for that box will have access to it, and only by looking it up by name (you won't see it in a list when looking at \\server). I suggest you get one of your mac users into that group temporarily, so you can at least test that share.