File and directory permissions

Even as an admin on a W2K TeamSite server, there are plenty of spots in the branching structure that I can't access (via W2K Explorer).

Is there a tool that can help me see permissions across the whole IFS share?

Find more posts tagged with

Comments

Adam Stoller

Can you provide some for-instance's
Also - what version of TeamSite (I don't think it matters in this case, but it's always a good idea to include that information)

--fish
(Interwoven, Curriculum Development)

msrich

We're using TS 5.0.1 on W2K server.

If I'm logged on at a workstation with a W2K ID (that happens to be defined as Master in TeamSite -- really of no bearing, I think) that's defined as a W2K administrator on the TS server box, and I make a network mapping ('net use') to the 'default' share on the server, I can navigate the server's backing store via W2K Explorer on my client machine. I can navigate down the branching structure -- and view permissions -- only when the ID I'm using happens to be a member of the group-for-sharing that was used in setting up the branch or workarea I'm trying to see. I don't necessarily need to be able to view files, but I'd really like to be able to see permissions across all branches and workareas.

Hope that helps. Thanks.

Adam Stoller

Let's start with the TeamSite server box itself (if you are able to login directly to it on its console?).

You log in as a Windows Administrator - bring up the Windows Explorer/browser - go to the Y:\ drive - what do you see?

If you see a directory "default" - and navigate into that - what do you see?
(repeat ad-nauseum)

At what point do you fail to see a list of files and/or directories? At a branch level? Staging? Editions? Workareas?

If you can provide an ASCII picture of the tree and where the problem occur, the might help too - e.g.:

Y:\default\main\devnet\STAGING\subdir1\subdir2
Y:\default\main\devnet\WORKAREA\wa1\subdir1\subdir2
Y:\default\main\devnet\WORKAREA\wa2\subdi1\subdir2
Y:\default\main\devnet\EDITION\INITIAL
Y:\default\main\devnet\EDITION\ed_001\subdir1\subdir2
...
etc.

You don't need the *whole* thing - but sufficient cases where things work and where they don't work in order to get an idea of where the problem might exist.

--fish
(Interwoven, Curriculum Development)