Access Denied On Trying To Execute A File On A Network Share

Question

_{Thursday, May 31, 2018 12:15 PM}

Hey everyone,  we have a very weird situation.  We have user "Bob".  Bob has mapped a network drive say drive O:\ When he goes to the O:\ He can view contents and can modify files.  However when Bob goes to the mapped drive and executes a program he gets access denied.  He has full rights to this share.  Bob can go to another workstation and log in and everything works fine.  User "Joe" who owns the "working" computer, goes to Bob's computer and has the same result as Bob.

I have also checked with own account and can produce the same result.  We are assuming that users have installed an application or some setting has changed on the workstation, but have no idea.  All of our searches are in vain.  

Ideas?

Thanks

All replies (2)

_{Friday, June 1, 2018 2:04 AM}

Well, Bob’s account is fine, Joe’s account and machine are fine, everyone that login Bob’s device will have issue to open .exe in share folder.

So, clean boot Bob’s computer, login system with a new admin account, visit share folder via server address, test again, don’t map share folder.

If you can execute program this time, do the following steps:

Start a command prompt as administrator first. From there enter the following command:

net use g: \server\share

Replace the drive and share so they match your existing share.

As long as this command prompt window is open, execute your executable as administrator.

If still cannot execute program, run process monitor to track “Access Denied” Registry and File Events.

Using Process Monitor to solve any problem, including DebugDiag

https://blogs.msdn.microsoft.com/benjaminperkins/2013/05/03/using-process-monitor-to-solve-any-problem-including-debugdiag/

Process Monitor v3.50 is the latest version, it’s easy to download it from here:

/en-us/sysinternals/downloads/procmon

Regards

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Wednesday, August 22, 2018 1:26 PM}

Did you find a solution to this?  I'm seeing the same thing.