W2K Adv Server - Sharing and Permissions

munman

Junior Member
Aug 3, 2000
5
0
0
Have Advanced Server w/ SP1 and am having strange problems with sharing/Permissions/Security.

I am intermittently and inconsistently unable to view shared folders. To clarify, I have folders set up to share with the appropriate security and Everyone set in permissions. No matter what user log on I use, I am unable to SEE (not just access, but SEE) the folders. I have tried many combinations such as enabling permission and security for a single user(instead of Everyone), groups, etc (am using a domain controller). Have tried to account for inherited issues, but this does not seem to help.

The strange part is that sharing/security works as expected for SOME folders/directories, but not others. Seems that I can see the SAME folders for every user, no matter how I set up the sharing and security. And there is no discernable difference in sharing/security configurations between a folder that does work, and one that does not.

I am new to Advanced Server and setting permissions/security, and would appreciate help.

Thanks!!
 

celeritas

Senior member
Oct 13, 1999
935
0
0
Are the shares you cannot see on the root of the drives/partitions? Do the share names end with a $? $'s are on the end of root shares by default; e.g., C$, D$, etc. They make your shares invisible on a network... If that's what's going on in your case, you'll either have to include the $ when you try to map a drive, etc. from clients, or create a new share on the server that doesn't have a $ on the end.

Since you mentioned that it's an intermittent problem, perhaps the above doesn't apply to you -- but it's good info, regardless. :)
 

setaanbomb

Banned
Oct 24, 2000
284
0
0
Note, Shares that end with the $ sign are established as invisible. This means you have to know the exact path to the share. Ex: \\DomainWidget\D$.

Use invisible shares when you don't want users to be able to browse the network and see the shares.
 

celeritas

Senior member
Oct 13, 1999
935
0
0
I think if you make NetBEUI the default protocol on the box, bind M$ Client & F&P sharing to NetBEUI (unbind both from TCP/IP), and disable NetBIOS over TCP/IP, that'll have a similar effect...

TCP/IP clients from the internet won't be able to see/access the shares, and I believe that local clients who are using TCP/IP as the default protocol, etc. won't be able to see/access them, either. I've only tested this on a couple machines, though. Is that everyone else's experience too?