Application access problem on peer-to-peer network

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

On my 12 workstation peer-to-peer network I have Windows 2000 Professional on all PCs. There is a shared folder on one of the hard drives for data files used by a third party application running on the remaining 11 PCs. This shared folder is set for "read only" by users.

If I'm logged-in as an administrator on the "clients" I can view the shared folder, select files, tell the application to open a file file, and the application will run normally

However, if I'm logged-in as a user the application crashes as soon as I tell the application to open the file. I have Dr. Watson running in the background and it reports an "access violation." (Needless to say, the application runs without incident if the data file is on the same hard drive as the app.

This appears to be a permissions problem with the user account, as that's the only difference between the two accounts. I'm not sure where in the user permissions the problem lies. None of the articles on the MS site I've found deal with application errors over networks. Suggestions anyone?? Thanks in advance.
 
Make sure that the user accounts with the same logon name/password exist on
the computer offering the share as what the user logs onto their local
computer with. Also try increasing the ntfs permissions to read/list/execute
which still will not allow users to create or delete files in that share.
Filemon from Sysinternals may also help show where the problem lies if you
continue to have problems by running it with the "runas" command while
logged onto the computer as a regular user just before trying to access that
share. --- Steve

http://www.sysinternals.com/

John S. Baker said:
On my 12 workstation peer-to-peer network I have Windows 2000 Professional
on all PCs. There is a shared folder on one of the hard drives for data
files used by a third party application running on the remaining 11 PCs.
This shared folder is set for "read only" by users.
If I'm logged-in as an administrator on the "clients" I can view the
shared folder, select files, tell the application to open a file file, and
the application will run normally.
However, if I'm logged-in as a user the application crashes as soon as I
tell the application to open the file. I have Dr. Watson running in the
background and it reports an "access violation." (Needless to say, the
application runs without incident if the data file is on the same hard drive
as the app.)
This appears to be a permissions problem with the user account, as that's
the only difference between the two accounts. I'm not sure where in the
user permissions the problem lies. None of the articles on the MS site I've
found deal with application errors over networks. Suggestions anyone??
Thanks in advance.
 
When your application crashes on an "access violation" I believe that's a
memory access violation and usually if your drwtsn32 is configured for it, a
user.dmp will be generated. Your application vendor may be able to debug
that memory dump to determine the cause of the problem.

(JD)

John S. Baker said:
On my 12 workstation peer-to-peer network I have Windows 2000 Professional
on all PCs. There is a shared folder on one of the hard drives for data
files used by a third party application running on the remaining 11 PCs.
This shared folder is set for "read only" by users.
If I'm logged-in as an administrator on the "clients" I can view the
shared folder, select files, tell the application to open a file file, and
the application will run normally.
However, if I'm logged-in as a user the application crashes as soon as I
tell the application to open the file. I have Dr. Watson running in the
background and it reports an "access violation." (Needless to say, the
application runs without incident if the data file is on the same hard drive
as the app.)
This appears to be a permissions problem with the user account, as that's
the only difference between the two accounts. I'm not sure where in the
user permissions the problem lies. None of the articles on the MS site I've
found deal with application errors over networks. Suggestions anyone??
Thanks in advance.
 
Back
Top