T
Travis Ausen
I'm using an application that can run as local system
account. It will also use logged in user credentials to
access network resources. However I'm noticing that even
when logged off the application is still able to access
network resources if any of the following groups have
read privileges to the resources. The groups I've tried
and tested would be Everyone, Network, or Authenticated
Users.
I'm not creating Null Session Shares by editing the
registry to allow Null Shares on the particular
resource. However, recently I've been to a seminar
regarding Windows Server 2003. Part of the conversation,
I missed part of it, talked about restrictanonymous is
this effecting my logged off PC?
I don't want the application I'm using accessing the
network resource without supplied credentials. I could
change the user rights and remove either Everyone,
Network, or Authenticated Users. But, I'd like to
understand how or why this application is getting access
to this network resource via those groups.
account. It will also use logged in user credentials to
access network resources. However I'm noticing that even
when logged off the application is still able to access
network resources if any of the following groups have
read privileges to the resources. The groups I've tried
and tested would be Everyone, Network, or Authenticated
Users.
I'm not creating Null Session Shares by editing the
registry to allow Null Shares on the particular
resource. However, recently I've been to a seminar
regarding Windows Server 2003. Part of the conversation,
I missed part of it, talked about restrictanonymous is
this effecting my logged off PC?
I don't want the application I'm using accessing the
network resource without supplied credentials. I could
change the user rights and remove either Everyone,
Network, or Authenticated Users. But, I'd like to
understand how or why this application is getting access
to this network resource via those groups.