SBS File Share issue with subdirectories 1

[benedictw]

We code a particular small program - the problem is that it works fine - when run on the server on the share. The program runs FINE from a workstation but fails when it accesses a subdirectory.

I can replicate the problem with good old Notepad (IE file access within the share directory is fine, file access within the subdirectory fails).

The program is accessed from \\servername\sharename
The files that fail are in \\servername\sharename\subfoldername

My thought is that there is some sort of sharing\file permissions issue going on. As a tempory measure the server admin made the user into an administrator - but this seems to have made almost no difference.

Any ideas?

 

[ShackDaddy]

When you get properties on the subdirectory and look at the Security tab (while on the server), you should see permissions that would allow the sort of access that you are expecting. Do you?

Is the program accessing the file via UNC paths, or is it using file:/// style paths with a browser? Are you creating hyperlinks of some sort?

ShackDaddy
Shackelford Consulting

 

[benedictw]

Hi ShackDaddy,

We're using the Win32 File api and using UNC paths.

The security tab on the server shows the all the permissions set to 'Allow'.

Thanks

Ben

 

[benedictw]

Heres the complete dump of the security settings for the shared folder (from the security tab)

Admin: All Allow
Everyone: All Allow
Users: All Allow

File sharing permissions: All Allow

Subfolder:
All Allow - but in grey EXCEPT for CREATOR OWNER for which neither allow not deny are set (except for special permissions).

 

[benedictw]

This morning I've gone onto the workstation and it more or less behaves as expected - notepad can save a file, folders can be created, zips can be expanded - none of which worked yesterday.

 

[benedictw]

Finally found what the problem was:
Some files seemed to be flagged as system admin only. Setting these files to include the Users group fixed the problem.

 

[ShackDaddy]

Glad this was resolved. There was really no other explanation I could think of besides permissions.

ShackDaddy
Shackelford Consulting