Permissions on hidden shares

From: Alan (a.bourgeois@ssss.com)
Date: 01/22/03


From: "Alan" <a.bourgeois@ssss.com>
Date: Wed, 22 Jan 2003 13:47:39 -0600


We have a NT 4.0 domain with Win2k clients and we have various people who
can map to other users hidden shares (c$) on the 2000 client machines. None
of the users are in any administrative groups. They are not able to connect
to every 2000 client though. We use a RIS server and Ghost to create our
images so the computers should be the same. They are not able to connect to
the NT servers. I also work for another company that has NT servers and 2000
clients and they seem to have the exact same problem. I checked the
permissions on the hidden share and it does not show the everyone group on
the hidden share. Any ideas?



Relevant Pages

  • Re: [fw-wiz] Defense in Depth to the Desktop
    ... > network hardware mechanisms. ... The Strong Internal Network Defense ... The client subnet and the server ... Servers are allowed to reply to clients, ...
    (Firewall-Wizards)
  • [fw-wiz] Defense in Depth to the Desktop
    ... network hardware mechanisms. ... controls is highlighted when the internal network and systems suffer ... The client subnet and the server ... Servers are allowed to reply to clients, ...
    (Firewall-Wizards)
  • Re: [fw-wiz] Defense in Depth to the Desktop
    ... Sounds a lot like Domain Based Security (not Windows 'domains', ... > network hardware mechanisms. ... The client subnet and the ... Servers are allowed to reply to clients, ...
    (Firewall-Wizards)
  • Re: What doesnt lend itself to OO?
    ... objects need to be explicitly maintained....thus the rise of stateless ... of state largely the responsibility of the client. ... object only exists on 1 out of n servers the load balancer needs to ...
    (comp.object)
  • Re: 1058 and 1030 errors revisited
    ... Are you sure about the symptoms ie when the11th or 12th user logs ... Does the issue occour only on some machines? ... We have four servers to ... There are about sixty client ...
    (microsoft.public.windows.group_policy)