Local PC Process across a network

we have a software product that runs an executable program as a process on a Local Client. The client accesses shared folders across the network on another Network PC via .LOC files (location files, pointers to the shares) that reside on the local client.

The process then runs for a couple of minutes and then fails (Process Ends) indicating that the process cannot access the data on the other network PC.
The other Network PC, which contains all of the data and also an identical local executable process works ok as the data is on this machine.

My question is:
Can a local process access shared data folders across a network?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

David Johnson, CD, MVPOwnerCommented:
define local process?  What user is it running as? System?  The account must have access to the share.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
David_J_GAuthor Commented:
Hi David,
Thanks for the reply. The current logged in user starts to process by running the executable from the software. This enables the process to run in the background and browse the shared folders every 45 secs. It will then interact with them if it finds any data it can work with.

Therefore the process is running as the current logged in user. The users do have access to the shares.
Qlemo"Batchelor", Developer and EE Topic AdvisorCommented:
Try to get some debugging logs from the application.
Or use SysInternals Process Monitor with a filter "Process Name", "is", "yourprocess.exe", and let the process run. This will reveal anything the process requests access to, with success or failure.
Check Out How Miercom Evaluates Wi-Fi Security!

It's not just about Wi-Fi connectivity anymore. A wireless security breach can cost your business large amounts of time, trouble, and expense. Plus, hear first-hand from Miercom on how WatchGuard's Wi-Fi security stacks up against the competition plus a LIVE demo!

David_J_GAuthor Commented:
The issue here was very basic and just user permissions.
Thanks for suggestions.
David_J_GAuthor Commented:
I've requested that this question be closed as follows:

Accepted answer: 0 points for David_J_G's comment #a40802679

for the following reason:

We did not get to delve deeply into the processes as suggested as a permissions issue was detected when we went to another system.
David Johnson, CD, MVPOwnerCommented:
my answer http:#a40787696 directly stated that the user must have permissions
David_J_GAuthor Commented:
'Directly' is a little strong but I'm not up for any arguments so thank you for your input :-)
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.