Re: c:\winnt\system32\drivers\etc\

The .sam files are just sample files. Outside of that, I have no idea what
would happen in not allowing the built-in users group the ability to read
the hosts and lmhosts files. (Basically our site has DNS and WINS so we
don't use them under 'normal' conditions.)

"Will" <westes-usc@xxxxxxxxxxxxxx> wrote in message
news:Xe6dnSyg5MLxND3eRVn-sw@xxxxxxxxxxxxxxx
>I don't want someone with user privileges getting a map of IP and NETBEUI
> hosts out of the files in that directory.
>
> Your answer is clear for services. What about hosts and the lmhosts.sam?
> I guess I could just protect those files individually rather than the
> whole
> directory.
>
> --
> Will
>
>
> "neo [mvp outlook]" <neo@xxxxxxxxxxxxxxx> wrote in message
> news:#vB85$KAGHA.436@xxxxxxxxxxxxxxxxxxxxxxx
>> Considering that the built-in users group only gets read and execute
> rights
>> to this folder, what are you trying to accomplish by taking that away?
>>
>> To answer your question, we have some applications that look to the
> services
>> file to ensure that the port number is listed for their purpose. If it
>> isn't listed the app doesn't work. So in this case, if a user didn't
>> have
>> read rights to that file, they couldn't run our app because the
> application
>> wouldn't be able to access the file.
>>
>> /neo
>>
>> "Will" <westes-usc@xxxxxxxxxxxxxx> wrote in message
>> news:6LGdnW9_srLKIgLenZ2dnUVZ_tmdnZ2d@xxxxxxxxxxxxxxx
>> > Does the Windows 200x BUILTIN\Users group need access to
>> > c:\winnt\system32\drivers\etc\ ?
>> >
>> > I would like to restrict access to this group to Administrators and
>> > SYSTEM.
>> >
>> > --
>> > Will
>> >
>> >
>>
>>
>
>


.