Why does a domain user get an UnauthorizedAccessException with read and write permissions granted to Everyone?

Question

Our application allows users to read and write files to share on \\ foo \ bar $. The administrator has granted "everything" permissions for reading and writing on the Allow Access and Security tabs. When a domain user tries to write this resource, our application logs the following:

TYPE: System.UnauthorizedAccessException MSG: Access to the path '\\foo\bar$\00074458_00076402.tif' is denied. SOURCE: mscorlib SITE: WinIOError at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.File.InternalCopy(String sourceFileName, String destFileName, Boolean overwrite) at Ceoimage.Basecamp.DocumentServers.DirectAccessServer._TryCommitQueueFile(IDocQueueFile file) at Ceoimage.Basecamp.DocumentServers.DirectAccessServer.SendQueuedFiles(Int32 queueId, Int32 userId, IDocQueueFile[] queueFiles) at Ceoimage.Basecamp.ScanDocuments.DataModule.CommitDocumentToQueue(QueuedDocumentModelWithCollections queuedDocument, IDocQueueFile[] files) 

I don’t have a domain account, so I can’t check the effective permissions of this user, but does “Everyone” apply to domain users? Do domain users need to authenticate with the server in addition to Active Directory if "everyone" is considered a local director? Is he a local director?

Our application is a .NET WinForms application running on a Windows 7 client in a Windows domain, trying to access a file server running Windows Server 2008 R2 Standard SP 1. If you cannot tell, I'm a little tired of my depth.

Answer 1

Ah, complicated resolution ..

I had to deal with this problem for quite some time. Here's the cause of the problem: LDAP works in a GUID. The group of administrators, of course, will have a different landmark than the one that is currently present in the domain.

This problem occurs because the machine has stopped synchronizing, or because the files were simply transferred from the previous machine to a new assembly (another hard drive).

There is a fix!

I would add catch and inside, I would take responsibility for the files and re-apply the domain policy from scratch.

I did this recently, if you need more information let me know.