Protecting Folders

[Guest]

I have a question about password protecting a shared folder on a corporate
domain. Now i know that I can always just set the permissions. The problem
with that in this case is that I cannot always log my users out to log myself
in and frankly I am just to lazy to map a network drive and then disconnect
it. Does anyone know of a program that will password protect the said share
and allow me to access it remotely using the password?

 

[Lanwench [MVP - Exchange]]

In

I have a question about password protecting a shared folder on a
corporate domain. Now i know that I can always just set the
permissions. The problem with that in this case is that I cannot
always log my users out to log myself in and frankly I am just to
lazy to map a network drive and then disconnect it. Does anyone know
of a program that will password protect the said share and allow me
to access it remotely using the password?

No, there's no native way to password protect your folders; NTFS permissions
are how it's done, and it really shouldn't be that big a deal. If you have a
domain, and servers, all your data should be on the server (not on a
workstation) - and your users wouldn't normally be able to log into the
server in the first place. If you don't want to sit at the server to do it,
do this via remote desktop to the server, rather than while logged in as
yourself at a desktop & across a mapped drive connection.

 

[Guest]

In

No, there's no native way to password protect your folders; NTFS permissions
are how it's done, and it really shouldn't be that big a deal. If you have a
domain, and servers, all your data should be on the server (not on a
workstation) - and your users wouldn't normally be able to log into the
server in the first place. If you don't want to sit at the server to do it,
do this via remote desktop to the server, rather than while logged in as
yourself at a desktop & across a mapped drive connection.




Thanks for the response Lanwench it does indeed look like we are just going to have to go with the mapped drive scenario......darn those extra mouse clicks and key strokes.

 

[Lanwench [MVP - Exchange]]

In
Why wouldn't you just set up the permissions you need once, while at the
server via RD or directly at the console? I can't think that this would be a
regular, recurring task.

 

[Ron Lowe]

"Lanwench [MVP - Exchange]"

In

Why wouldn't you just set up the permissions you need once, while at the
server via RD or directly at the console? I can't think that this would be
a regular, recurring task.

He'd describing the situation where he ( as an admin ) goes over to a client
PC. The client PC is logged on as Joe User. The admin wants to grab
something from a secure share on a server, but since we're currently logged
in as Joe User, we can't; we don't have permission.

He has to either log off Joe User and log on as himself, grab the file, log
off and back on as Joe User; or temporarily map a network drive supplying
alternative credentials.

What he wants is a simple way to supply credentials when connecting to a
share.

If the client PC already has a connection to the server ( to another share )
using Joe User's credentials, it's not possible to connect to another share
on the same server using different credentials. If there is no existing
connection to the server, he should be prompted to supply credentials,
although this can be flakey. Ive seen situations where the user is not
prompted for credentials, and the connection is refused as 'access denied'
with no opportunity to supply credentials.


In answer to the OP: there's not much you can do other than what you are
currently doing.

 

[Lanwench [MVP - Exchange]]

In

"Lanwench [MVP - Exchange]"

In

Why wouldn't you just set up the permissions you need once, while at
the server via RD or directly at the console? I can't think that
this would be a regular, recurring task.

He'd describing the situation where he ( as an admin ) goes over to a
client PC. The client PC is logged on as Joe User. The admin wants
to grab something from a secure share on a server, but since we're
currently logged in as Joe User, we can't; we don't have permission.

He has to either log off Joe User and log on as himself, grab the
file, log off and back on as Joe User; or temporarily map a network
drive supplying alternative credentials.

What he wants is a simple way to supply credentials when connecting
to a share.

If the client PC already has a connection to the server ( to another
share ) using Joe User's credentials, it's not possible to connect to
another share on the same server using different credentials. If
there is no existing connection to the server, he should be prompted
to supply credentials, although this can be flakey. Ive seen
situations where the user is not prompted for credentials, and the
connection is refused as 'access denied' with no opportunity to
supply credentials.

In answer to the OP: there's not much you can do other than what you
are currently doing.

Ah; that wasn't clear to me; thanks. If the server's running W2003, he can
also use remote desktop w/drive redirection enabled, I guess.

 

[Guest]

In

"Lanwench [MVP - Exchange]"

In Spifford <[email protected]> typed:
:

In Spifford <[email protected]> typed:
I have a question about password protecting a shared folder on a
corporate domain. Now i know that I can always just set the
permissions. The problem with that in this case is that I cannot
always log my users out to log myself in and frankly I am just to
lazy to map a network drive and then disconnect it. Does anyone
know of a program that will password protect the said share and
allow me to access it remotely using the password?

No, there's no native way to password protect your folders; NTFS
permissions
are how it's done, and it really shouldn't be that big a deal. If
you have a
domain, and servers, all your data should be on the server (not on
a workstation) - and your users wouldn't normally be able to log
into the
server in the first place. If you don't want to sit at the server
to do it,
do this via remote desktop to the server, rather than while logged
in as
yourself at a desktop & across a mapped drive connection.




Thanks for the response Lanwench it does indeed look like we are
just going to have to go with the mapped drive scenario......darn
those extra mouse clicks and key strokes.

Why wouldn't you just set up the permissions you need once, while at
the server via RD or directly at the console? I can't think that
this would be a regular, recurring task.

He'd describing the situation where he ( as an admin ) goes over to a
client PC. The client PC is logged on as Joe User. The admin wants
to grab something from a secure share on a server, but since we're
currently logged in as Joe User, we can't; we don't have permission.

He has to either log off Joe User and log on as himself, grab the
file, log off and back on as Joe User; or temporarily map a network
drive supplying alternative credentials.

What he wants is a simple way to supply credentials when connecting
to a share.

If the client PC already has a connection to the server ( to another
share ) using Joe User's credentials, it's not possible to connect to
another share on the same server using different credentials. If
there is no existing connection to the server, he should be prompted
to supply credentials, although this can be flakey. Ive seen
situations where the user is not prompted for credentials, and the
connection is refused as 'access denied' with no opportunity to
supply credentials.

In answer to the OP: there's not much you can do other than what you
are currently doing.

Ah; that wasn't clear to me; thanks. If the server's running W2003, he can
also use remote desktop w/drive redirection enabled, I guess.

Thanks for the help, finally just decided to go with the standard practice
of mapping the drive without reconnect at login checked and just rebooting
the PC, which as you know for a user this is almost always needed anyway.
And I also just realized that I never even gave the specs, we are WinXP SP2
operation on all of our clients and the server I am connecting to for data is
a Dell Optiplex running Win2003 strictly for file server purposes. Once
again thanks for the suggestions.