Not allow non-domain computers to access W2K3 file shares regardless of user

The user has rights to access the data on a machine provided to them by us.
They cannot attach a USB drive, burn a CD, or FTP/email out information
without it being flagged/stopped.

So I was asked "What if Joe User brings in his home laptop?"
If a user does, and copies the IP settings from their corporate desktop,
then plugs in their laptop into the same wire and attempts to access a
Windows file share, they are prompted for a username and password. Since they
are a user with valid credentials, they can access the data and
hypothetically copy it and remove it from the building without us knowing.

How can I block a valid user from accessing a file share on a non-AD domain added machine?
OnvioAdminAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Renato Montenegro RusticiIT SpecialistCommented:
I dont thing you will achieve that using only AD. You need some switch features like Cisco's Port Security:

http://www.nsa.gov/snac/os/switch-guide-version1_01.pdf

This way, the user cant plug the computer in and therefore, cant access your resources.
0
tigermattCommented:
As far as I can see, I agree with the above post. Windows will automatically allow any authenticated user to access files and folders over which they have permissions, regardless of the machine they are working at. The behaviour you are seeing would be expected - when the user does not authenticate, they will be prompted for credentials.

You will need some kind of firewall or feature like what is mentioned in the post above. There's no easy way of achieving this, and even if there is you would need some rather complex, complicated permissions which would start getting over restricive on yourself.

-tigermatt
0
Joediggity2Commented:
One possible solution is to use Windows Rights Media.  In reality, the only way to completely lock it down is to only allow access from the specific machine and have no printers or outside communicaitons on that machine.  If someone can see the informaiton on their screen, they can take a screen shot of it (either from windows or using a third party app).  They can then save the screen shots as a different files and do what they want with it.
0
LauraEHunterMVPCommented:
You can accomplish this using a combination of Active Directory and an internal PKI by deploying Server and Domain Isolation - only domain-joined computers are issues a particular type of PKI certificate, and if a computer does not possess said it is not allowed to connect to one or more servers that you specify.  SDI is non-trivial to deploy and needs to be fully tested in a lab setting so that you are not inadvertently locking out legitimate users from accessing the resources they need: http://www.microsoft.com/technet/security/guidance/architectureanddesign/ipsec/default.mspx
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.