Secure files that must have read/write access?

  • Thread starter Thread starter Bill
  • Start date Start date
B

Bill

I have a set of files on a Windows XP Pro machine that serves as the
file server in a very small network. A folder contains a set of files.
Users must have read/write access to these files in order to run a
program that uses the files. The files are accessed via a mapped drive.
I want to make it as difficult as possible for someone to find and copy
these files. What is the best way to do this?
 
From: "Bill" <[email protected]>

| I have a set of files on a Windows XP Pro machine that serves as the
| file server in a very small network. A folder contains a set of files.
| Users must have read/write access to these files in order to run a
| program that uses the files. The files are accessed via a mapped drive.
| I want to make it as difficult as possible for someone to find and copy
| these files. What is the best way to do this?
|

Upgrade to a "real" server and use Domain Accounts in conjunction with NTFS Permissions and
NT Share permissions.
 
David said:
Upgrade to a "real" server and use Domain Accounts in conjunction
with NTFS Permissions and NT Share permissions.

By "real server" I assume you mean Windows Server 2003. What can I do
to obscure these files that everyone requires read/write access on
Windows Server that I cannot do with XP?

Note that this is a _very_ small organization with _very_ limited
resources. An enterprise solution is out of the question here. What I
need is suggestions that will achieve the best possible with the
environment that exists.
 
From: "Bill" <[email protected]>

| David H. Lipman wrote:
||
| By "real server" I assume you mean Windows Server 2003. What can I do
| to obscure these files that everyone requires read/write access on
| Windows Server that I cannot do with XP?
|
| Note that this is a _very_ small organization with _very_ limited
| resources. An enterprise solution is out of the question here. What I
| need is suggestions that will achieve the best possible with the
| environment that exists.
|

Using a server solution provides access control. Only those with privileges can access what
they are supposed to access and deny access to those who should not.

There are small business versions of Microsoft's server offerings.
 
Bill said:
By "real server" I assume you mean Windows Server 2003. What can I do
to obscure these files that everyone requires read/write access on
Windows Server that I cannot do with XP?

Note that this is a _very_ small organization with _very_ limited
resources. An enterprise solution is out of the question here. What I
need is suggestions that will achieve the best possible with the
environment that exists.

You can use Linux with SAMBA.

Dennis
 
Back
Top