[Samba] RE: W2K3 SP1 - PERSISTENT CONNECTION(S) BUG?

[bchapple at EWC.EDU]

This should be included in the weekly report.

Bernard 

-----Original Message-----
From: Michael Joyner [mailto:mjoyner at vbservices.net] 
Sent: Monday, May 02, 2005 8:20 AM
To: samba at lists.samba.org
Cc: Cook, Marvelle L; Mitchell, Joe A <jamitchell at EWC.EDU>; EWC Support;
jsklein at mindspring.com; jaxlug-list at jaxlug.org; Ben Maschan; Chapple,
Bernard <bchapple at EWC.EDU>
Subject: W2K3 SP1 - PERSISTENT CONNECTION(S) BUG?

After testing my W2K3 SP1 terminal server against a SAMBA server *AND* a
W2K server, I have noticed the following *odd* behavior.

LOGIN: Map drive letters
LOGOUT: Connections are still connected. on BOTH W2K and SAMBA file
servers.

LOGIN: Map drive letters
LOGOUT: Now you have TWO sets of connections still connected for the one
  user.

REPEAT: For each time you repeat the above procedure, you end up with
"persistent" connections from the W2K3 SP1 system! Now imagine a system
with 50+ users logging in and out all day long!

If you REBOOT the W2K3 SP1 system, all the connections are properly
disconnected.

If you run net use * /delete /yes, all the connections are properly
disconnected.

PROBLEM: This causes "resource exhaustion" on the SAMBA server. (And
probably on the W2K server as well, haven't tested it that far yet.)

MITIGATION: I added a policy that runs the following command on user
logout:

net use * /delete /yes

This seems to *mostly* elimate the persistent, resource exhausting, and
totally useless connections.

Is this a W2K3 SP1 bug?
An intentional change in behavior?

Is there anything I can do on the SAMBA side to enable detection of
these "should be disconnected" persistent connections for logged out
users and elimate them?

(I tried deadtime=1 and keepalive=1, but they stay connected anyways).

--
Michael Joyner/System Administrator
Edward Waters College