Jump to content

Recommended Posts

Posted

Hello,

 

Just curious if anyone has got any shares on their servers in which their students can write into but not read (if they created a shortcut to that share, for example).

 

We have a \\server01\logs$ area - which logs logins, logoffs and various other bits and bobs. The logs are written by vbs scripts run when a user logs on, off and at different times during their logon session. The VBS script writes to a log file.

 

Ideally, we'd like the students to be able to write to the log files and such, but if they tried to create a shortcut to \\server01\logs$ and then went through all the folders - they couldn't actually read the contents.

 

Bit of a contradiction in one sense, since they have to be able to read the file to write to it...but just wondered if anyone had got any suggestions?

 

We have ruled out disabling 'shortcut creation', as they use this in ICT lessons. We also know this logs location isn't public, so they'd have to guess it - but that might not take long really.

 

Running Windows 2003 network with XP clients.

Posted

Tried that but can't get it to work. The VBS script returns permission denied error. Hmm.

Thanks for your support none the less.

Posted
When you made the share you did set the share permissions to allow read write to everyone didn't you? Share permissions and security permissions are different.
Posted

Yes, share permissions - everyone has full control for.

Security permissions, ideally I want staff and students to be able to

Create Folders (as the script creates the folder if it isn't there.

Create Files (as the script creates the text file "Logs_Login_.txt")

Write/Append files and folders

 

But not view the folder contents if they create a shortcut and try and access them.

Posted

Could be your script, if it is appending to the log then it needs read access to grab the last position in the file and write from there. If you are just writing a new file each time then it may work, its probably just the append that is getting you into trouble.

 

Also without view list rights it may have issues running the checks to see if the file and folder exist before writing (not sure on this one). Might be an idea to try it with all but list rights and see if it works that way, if the ifexists checks fail because of the lack of folder list permission then you could get around it by changing the script to simply try to open the file and make one if it can't - if it is not written like this already.

  • Thanks 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...