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

Conference noted::pwv50ift

Title:	Kit: Note 4229; Please use NOTED::PWDOSWIN5 for V4.x server
Notice:	Kit: Note 4229; Please use NOTED::PWDOSWIN5 for V4.x server
Moderator:	CPEEDY::KENNEDY

Created:	Fri Dec 18 1992
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	4319
Total number of notes:	18478

4192.0. "win95 clients won't disconnect" by SUFRNG::WSA028::DOWNING_L () Wed Mar 05 1997 07:53

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
4192.1	clarification	SUFRNG::WSA028::DOWNING_L		`Thu Mar 06 1997 13:45`	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?
4192.2		UTRTSC::SWEEP	I want a lolly...	`Mon Mar 10 1997 04:55`	3
	Yes, thats fixed in 5.0e eco 1 Adrie
4192.3	probably opportunistic locking	TOHOPE::WSA028::DOWNING_L		`Fri Mar 14 1997 14:14`	3
	I think it has to do with opportunistic locking, and will have the customer try a Windows 95 version of his DOS app.
4192.4	problem not described in ECO1 release notes	SUFRNG::WSA028::DOWNING_L		`Wed Mar 26 1997 15:10`	3
	In case someone goes looking for it, this problem is not described in the eco1 release notes.