Samba doesn't free network resource with XP clients

[Christopher R. Hertel]

On Fri, Feb 28, 2003 at 10:23:16PM +0100, Charles Bueche wrote:
> Hi,
> 
> I posted my problem to samba at samba.org as well, I think it boils down to
> the post below. Is there a known fix to this problem ?

That is an old message, and I am sure we would not have changed Samba to
send all connected SMB's a "disconnect".  Doing so can have very bad
consequences.  There is another Windows KB article which explains, for
example, that this causes clients of a W2K server that are behind a NAT to
have their sessions shut down if a new client connects.  The new client 
sends VC=0 and the W2K server (since it sees all connections as coming 
from a single IP) disconnects all the other clients.  Ouch.

Microsoft has a patch for this, I believe.

Anyway, I did not see your port to samba at samba.org so I have to guess that 
your server is keeping TCP connections open until they time out.  Is that 
correct?  Which problem are you trying to solve?

Chris -)-----

> =======================================================================
> On Tue, Sep 17, 2002 at 09:50:28PM +0400, Vladimir I. Umnov wrote:
> > Hello, Fredrik.
> > 
> > 
> > FA> Ah.. So that's the reason for some of the problems.. Why can't samba
> > FA> "correctly process nt status code"? Do you know?
> > Samba process nt status code, but besides nt status code must die send
> > many other commands, and there is no documention about this commands.
> > But Microsoft KB article says, that only nt status code processed
> > incorrectly. I think, this is a politics of Microsoft. They want kill
> > free software!!!
> > 
> > 
> > FA> Should it be a dword och a regular string in the registry?
> > >From KB article:
> > Start Registry Editor (Regedt32.exe).
> > Locate and then click the following key in the registry:
> > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanworkstation\
> > parameters On the Edit menu, click Add Value, and then add the following
> > registry value: Value name: EnableDownLevelLogOff
> > Data type: REG_DWORD
> > Radix: Hexadecimal
> > Value data: 1
> > Quit Registry Editor.
> 
> Ah. Now I think I get it ......
> 
> The new Microsoft redirectors use the "feature" of Microsoft SMB
> implementations that SessionSetup SMB with the VC number set to 0
> should terminate all previous sessions from the same client, 
> they don't bother to send a Logoff command any more.
> 
> We can change Samba to send all connected SMB's a "disconnect"
> message when we get a new VC=0 SessionSetup to fix this I think.
> 
> I will investigate further.
> 
> Jeremy.
> =======================================================================

-- 
Samba Team -- http://www.samba.org/     -)-----   Christopher R. Hertel
jCIFS Team -- http://jcifs.samba.org/   -)-----   ubiqx development, uninq.
ubiqx Team -- http://www.ubiqx.org/     -)-----   crh at ubiqx.mn.org
OnLineBook -- http://ubiqx.org/cifs/    -)-----   crh at ubiqx.org