I have a XP SP3 OS running pc as a terminal server (do not ask how) , there are different user accounts on it and people are connecting to a shared folder on samba server. Users are running an exe file and using the software which connects to an MS Sql server.
Sometimes and randomly users are getting exception error messages and some other access violation errors.
It seems very random such as sometimes there a few days without an error message.
What I noticed most when a user closes the software, sometimes other users can get an exception error message. Only the ones running the software on the same XP terminal server are getting these error messages.
The error message appears even when we kill the exe via task manager and the user runs the software again and browse some menus...
In order to get rid of the error messages, all the users running the software on the xp server closes the software and we do run a part of software that checks for users still seems to be connected to the Ms sql server , but in fact not and cleans some tables in the sql server.
Something I noticed that when users connect to samba server from the xp machine, in the smbstatus , I see different user names and same pid no per machine name.
So, connections are served via same samba daemon to the xp client eventhough the user accounts connected are diferent.
I checked for oplocks but always "none" is displayed in smbstatus oplock column. I think this is not an oplock problem but a pid vs user name problem.
I guess if a user closes a connection to samba share , other users connection from the same xp machine is being effected.
The reason I can think of is all the connections from a client is being served by the same samba daemon, at least this is what I make of from smbstatus...
As a solution , I need a way so that each different user is being served by a different samba daemon. As if each user is a different machine...
I would be so glad if someone would advise how ...
Thanks for reading.