[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference jamin::pw95ift

Title:	PATHWORKS for Windows 95
Notice:	PWW95 1.0A Available -- See notes 3.39 and 8.7
Moderator:	JAMIN::SYSTEMROM

Created:	Thu Nov 17 1994
Last Modified:	Thu Jun 05 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	646
Total number of notes:	2900

625.0. "Win95 clients won't disconnect their sessions" by SUFRNG::WSA028::DOWNING_L () Wed Mar 05 1997 10:56

cross posted to PW95IFT


I have a customer with a PATHWORKS for OpenVMS 5.0D ECO2 server that has
Windows 3.1, WFW, and Windows 95 clients.

When the Windows 95 clients log out of Windows 95, their session to the
PATHWORKS Server is not disconnecting.

They must do a NET SESSION \\pcnode /DELETE to make them go away.

The Win3.1 and WFW clients act normally.

The only transport they use is TCP/IP.

The clients are native Win95, just using the PATHWORKS licensing software.

Has anyone seen this before?

-Linda

T.R	Title	User	Personal Name	Date	Lines
625.1	clarification	TOHOPE::WSA028::DOWNING_L		`Thu Mar 06 1997 16:47`	16
	My customer and I had some difficulty communicating the first time... Here is the real issue: He has Borland Dbase v5.0 for DOS on a share on his PATHWORKS Server. He maps a drive to the share, runs the application, and exits from the application. From the client's point of view, they are back to their DOS prompt. ADMIN/PATHWORKS sees that the Windows 95 client still has files open in that application. The Windows 3.1 clients exited completely. anyone seen this?
625.2		JAMIN::WASSER	John A. Wasser	`Thu Mar 06 1997 16:57`	6
	> ADMIN/PATHWORKS sees that the Windows 95 client still has files open > in that application. A VMS "SHOW DEVICE device /FILES" on the device that contains the share should show which files are open. That might give a hint as to why they are open.
625.3		SPELNK::curless		`Thu Mar 06 1997 19:55`	7
	Quite probably they are still open as per the "File Open Cache", to increase the performance of the file share.... So, it's very likely they will close within some documented timeframe. Jeff
625.4		SUFRNG::WSA028::DOWNING_L		`Mon Mar 10 1997 10:58`	4
	its just strange that Windows 3.1 client close immediately, and Windows95 clients do not close their files upon exiting the application. Does 'File Open Cache' act differently based on what type of client is connected?
625.5		TOHOPE::WSA028::DOWNING_L		`Mon Mar 10 1997 11:12`	2
	note 4192.2 in pwv50ift indicates that this is a problem fixed in 5.0e eco1 of the Server.
625.6		SPELNK::curless		`Mon Mar 10 1997 16:54`	7
	Well, there you go... fixed. Depending on the redirector, Win3.1 would probably work differently than Win95 due to SMB versions. Jeff
625.7	can't tell what the truth is	TOHOPE::WSA028::DOWNING_L		`Thu Mar 13 1997 11:52`	2
	Well, it looks like the 5.0e eco1 release notes do not describe the fix. So, I'm back to where I started.
625.8		SPELNK::curless		`Thu Mar 13 1997 21:06`	5
	It's not in the release notes, but that does not mean it wasn't fixed, can anyone VERIFY if it does work with v5.0e? Jeff
625.9	maybe it has to do with opportunistic locking	TOHOPE::WSA028::DOWNING_L		`Fri Mar 14 1997 17:11`	9
	The reference to different SMB types led me to find a STARS/TIMA article which discussed Opportunistic locking (OpLocks) and how it effects Windows 95 clients running DOS apps on a PATHWORKS V5 server. The answer is he needs to use a Windows95 version of his application. Thanks for all your help, -Linda