Question

I work on a thick-client app that often runs into ‘issues’ accessing network shares. Before doing any IO with the server, my app tests whether the share (usually of the form \\server\share$) exists. This works fine for detecting those scenarios in which the client has lost its connection to the server, but there are still those odd scenarios where the hidden share exists but the user does not have the rights to read from the within the share. Can someone share (no pun intended) the C# code required to test whether the current user can read files on a share? Should I be querying the share’s ACL or the files within the share? What if the share is empty? What if the user is a local non-admin in a mixed environment (XP Pro workstation, Windows 2003 server without a domain on a Novell network)?

Answer 1

The easiest way is to just do it (i.e. try to read a file, for example). As Jared mentioned, there is no way to make sure that you will be able to read in the future (network failure, change of permissions, etc).

As far as code goes, you could use the DirectoryInfo class for some attempts at an answer:

        string remotePath = @'\\server\share$';         bool haveAccess = false;          DirectoryInfo di = new DirectoryInfo(remotePath);         if (di.Exists)         {             try             {                 // you could also call GetDirectories or GetFiles                 // to test them individually                 // this will throw an exception if you don't have                  // rights to the directory, though                 var acl = di.GetAccessControl();                 haveAccess = true;             }             catch (UnauthorizedAccessException uae)             {                 if (uae.Message.Contains('read-only'))                 {                     // seems like it is just read-only                     haveAccess = true;                 }                 // no access, sorry                 // do something else...             }         } 

There are many shortcomings in the above code (such as the hard-coded ‘read-only’ test), but it is just an example used to illustrate what you could do. DirectoryInfo has a few other helper methods that you can use to list the files in the folder. If you don’t have access, the methods will throw an UnauthorizedAccessException exception which you can use to test why the access failed. Check out the info on GetAccessControl for further details on the exceptions it throws.