Windows 2000 Server and shared folder with a protected sub-folder

[Paul McIlfatrick]

Not sure which win2000 newsgroup this should be posted to so sorry if this
is not the correct one.


At my wife's work they have Windows 2000 Workstation PCs working to a
Windows 2000 Server (PCs and Server are in the same workgroup).

I have created a shared folder on the Windows 2000 Server which all the
Windows 2000 Workstation PCs can access and they are able to read and update
the documents in that folder. Also in that shared folder I have created a
protected folder which I have set up with Server's Administrator and one
other user having full control access.


Is there a way to configure Windows 2000 Server so that when a user tries to
access the protected sub-folder within the shared folder a username/password
window will open rather than the "Access denied" message?


I have tried various options in the shared folder settings but cannot get a
username/password window to open and Googling hasn't turned up anything.

Would there a policy option available in Windows 2000 Server Group Policy
that would enable what I want?


Thanks


Paul McIlfatrick

 

[Roger Abell [MVP]]

Not sure which win2000 newsgroup this should be posted to so sorry if this
is not the correct one.


At my wife's work they have Windows 2000 Workstation PCs working to a
Windows 2000 Server (PCs and Server are in the same workgroup).

I have created a shared folder on the Windows 2000 Server which all the
Windows 2000 Workstation PCs can access and they are able to read and
update the documents in that folder. Also in that shared folder I have
created a protected folder which I have set up with Server's Administrator
and one other user having full control access.


Is there a way to configure Windows 2000 Server so that when a user tries
to access the protected sub-folder within the shared folder a
username/password window will open rather than the "Access denied"
message?

There is no way of which I have awareness.
The folder is configured to allow access to x, y, and z.
Someone comes along and the server sees they are a, b or c
and says sorry. Why would the server ask again who they
are when it believes they are who they are, a, b, or c ?
You probably would be better off making that storage a
separate share and showing those few that should have
access while logged in as some other account how they
map a drive with different credentials. However, in either
scenario what you will run upon is that a machine only will
allow one connection to a sharing machine at a time, meaning
that two different sets of credentials recognized by the remote
sharing machine cannot be in use at the same time for access
to shares.