Discussion Locked

Win9x Clients see too much in W2K Server

0 helpful
14 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a W2K File/Print Server connected to a W2K AD Domain with NT and 9x Clients. Though rights and privledges have been assigned properly (tested thoroughly with the NT clients), I am able to see the contents of folders (that I have no access to)from the Win9x Clients. I am unable to actually pull up the contents of the files in any given folder but I am able to see file names as well as sub-folders.

I have already installed the MS Active Directory Services Client on the Win9x machine. No change in problem.

14 replies

by joe_abdo

you said: "I am unable to actually pull up the contents of the files in any given folder but I am able to see file names as well as sub-folders"
in windows 2000 it's normal to see contents even if u don't have the right permission.
- u can see files from the client's PC because u set a share on this folder so don't worry.
- there is no other way to hide files names if u have to share this folder.
best regards
joe

by eldon

In W2K it IS NOT normal to see sub-folder and file names if a group is either not granted access or specifically denied access.

All of my Winnt and W2K clients are DENIED access to even view folder/sub-folder and file names to shares that the respective group has no access to. Win9x clients, however, are able to see ALL folders, subs and file names regardless of security permissions and group membership.

by saihib

OK, you've given a narrative, what's your problem?
Being able to see file names means read access. Is being able to read file names too much access?
Exactly what are you trying to conceal?

by eldon

The problem is as I've stated. From a Win9x machine, users are able to see folder and sub-folder names, as well as file names to folders that I specifically denied them access to. Is that too much access? Yes! Given this example... I am a manager about to fire Joe Blow, who has a Win9x PC. I create a pre-process termination file called... You guessed it, Joe Blow Termination. Now Joe goes into that share from his Win9x PC and sees that he's about to get canned (an HR nightmare). That's only oneexample.

On all of my Winnt and W2K machines, when I try to access the same shares (because of how permissions are set), I am explicitly DENIED ACCESS. That's what I'm looking for on the Win9x PCs. Does that help?

by hacbmis

If you create groups, it is much easier to to share things on the domian. Then you can give rights to how you what. When you setup user profiles assign them to groups,ie accouting, billing.............

by eldon

I am utilizing groups, etc. already. The issue is; As I currently have permissions configured, Winnt and W2K clients/groups are specifically DENIED access to folder to which they do not have access. Win9x clients, however, are able to scan folder/sub-folder and file names regardless of security permissions set on groups. Does that clarify?

by silentmisery

Have you tried denying access to the folders/files based on the W9x computer account, rather than group/user accounts? So when the W9x computer(s) in question try to access the resource, it is denied access.

by timwalsh

I have tried to duplicate your problem since I have a similar setup.
Server - Win2K AD
Client - Win 98SE (w/o AD services client)

Permissions (in this example - home directory):
Share: all permissions assigned only to owner
NTFS: Full Control allowed for owner and Domain Admin; Box next to "Allow inheritable permissions from parent to propagate to this object" unchecked.

Results: Wasn't able to duplicate the problem. When I (logged on as normal user) click a shared folder I don'thave access to, I get "Access is denied." When I browse to a higher level share that includes the direct access to the folder (vs. through a share), and try to access, I get the same result. I am unable to browse and see names of subfolders and files.

Did you get the same results without the AD client loaded? I can only think of 2 possibilities: 1) the AD client somehow allows you to bypass normal NTFS permissions (not likely - although it may allow you a different browsing mechanism than is normally available; I haven't installed it so I can't say); 2) Permissions (Remember that permissions are additive (least restrictive) - minus any expressly Denied). Double check the permissions (to include those under the Advanced window) on the folders in question.

Hope this helps / gives some more things to think about.

This discussion is closed to new replies.