Discussion Locked

mapping an NT drive to a remote pc

0 helpful
10 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am setting up an NT server with some CD-ROM based training applications. I want my clients to be able to remotely connect to the server to run only these apps (they will essentially be mounting a remote drive on the server.

However, I want tomake sure they can only run certain executables, and not transfer the CDROM files to their machines.

Is remote control software the answer (as in PCAnywhere or NetOP), or is there some simpler means? I have to control user security and accessas well.

My clients and I are all on a WAN (there is no dialup networking provision, so RAS is not going to be used)

10 replies

by bohicam1

I do not believe you can do that. Even if you transfer the files to a directory on the server and share them out, you cannot restrict users from copying the files...if you can read them, you can copy them.

by duwaned

The only way I can suggest doing this, is to implement a Terminal server accross the WAN, with major policy restrictions for the clients.

This would mean that you would have to remove basicaly all functionality from the client side except executing the short-cut to your training app for this method to be effective.

There are some other third party apps that allow this sort of functionality, but most of them are expensive, and unstable. I would stick with the Terminal server if I were you.

I hope this helps you.
Regards.
Duwane

by jrl2k

Share the CD drive and set the permissions to read only. However, running a CD over a WAN is going to be painfully slow.

Therefore, set up a Win2K server and crank up the Terminal Server service. Use the Policy Editor to restrict what the user can access. You can reduce remote user access to the desktop where only shortcut to your Training CD exists. This will prevent them from copying files.

by vagab0nd

Do you really need to map a drive? Just create a shortcut to hidden share (eg. \\server\cd$) on desktop that will run the app. Your users won't even find any files.

This discussion is closed to new replies.