samba - Oct 2004 - random errors "the local drive name is already in use. This connection has not been restored."

Hello,
 
I have random errors that I can not analyze nor fix:
when several users connect to the same Samba share, they get sometimes 
error messages
"the local drive name is already in use. This connection has not been 
restored", although the connection
is still usable afterwards. This sometimes breaks a file operation.
Clients are running Windows 2000, and the server is a Solaris 8 machine, 
it runs Samba 3.0.4.
After this I can often see that Samba still holds locks about files which 
are not used any more.
 
Is this a known symptom for Samba 3.0.4 ?
I have seen that many bugs are fixed in newer Samba versions, but I can 
not tell if they could be related to my problem.
 
In fact the problem might be related to code I wrote: my Samba is 
configured to load a specific VFS module,
which makes external database queries, among other things.
As a result the file operations are quite slow, and the result of some 
file operations may not be 100%
as Samba or Windows expect them to be....
 
Would you know a way to sort out the problem, e.g. something like a 
SMB protocol analyzer (for networking newbies...) ?
Or a way to know why Windows clients disconnect (if they decide to 
disconnect, rather than get disconnected) ?
Or would you know problems about slow Samba servers ?
 
Thanks in advance for your answers,
Yves Lejeune.
yves.lejeune@kodak.com

I have had this problem unrelated to samba. I believe it is in the login
scripts. Perhaps you are using the "net use /persistent" switch when
you do no need to?

Regards,

Gerald Bird

----- Original Message -----
From: yves.lejeune@kodak.com
Date: Tuesday, October 5, 2004 11:05 am
Subject: [Samba] random errors "the local drive name is already in use.
This connection has not been restored."
> Hello,
> 
> I have random errors that I can not analyze nor fix:
> when several users connect to the same Samba share, they get 
> sometimes 
> error messages
> "the local drive name is already in use. This connection has not 
> been 
> restored", although the connection
> is still usable afterwards.

Try using:

net use * /delete /yes

Before mapping any drives in the login script.  This will clear any drives
already mapped.  I do this in my login script to get rid of the drives that
XP/2k will sometimes hold on to and not let go on reboot.

- Brad
----- Original Message ----- 
From: "Gerald Bird" <rocknrollgolfer@shaw.ca>
To: <yves.lejeune@kodak.com>
Cc: <samba@lists.samba.org>
Sent: Tuesday, October 05, 2004 12:14 PM
Subject: Re: [Samba] random errors"the local drive name is already in use.
This connection has not beenrestored."

> I have had this problem unrelated to samba. I believe it is in the login
scripts. Perhaps you are using the "net use /persistent" switch when
you do
no need to?
>
> Regards,
>
> Gerald Bird
>
> ----- Original Message -----
> From: yves.lejeune@kodak.com
> Date: Tuesday, October 5, 2004 11:05 am
> Subject: [Samba] random errors "the local drive name is already in
use.
This connection has not been restored."
>
> > Hello,
> >
> > I have random errors that I can not analyze nor fix:
> > when several users connect to the same Samba share, they get
> > sometimes
> > error messages
> > "the local drive name is already in use. This connection has not
> > been
> > restored", although the connection
> > is still usable afterwards.
>
>
>

I think this is possibly a windows problem, I have had the same error in 
high usage workgroup situations with win2000. There is a relatively 
simple fix, I think if you search MS for the error message it is there.
H

Brad Otto wrote:
>Try using:
>
>net use * /delete /yes
>
>Before mapping any drives in the login script.  This will clear any drives
>already mapped.  I do this in my login script to get rid of the drives that
>XP/2k will sometimes hold on to and not let go on reboot.
>
>- Brad
>----- Original Message ----- 
>From: "Gerald Bird" <rocknrollgolfer@shaw.ca>
>To: <yves.lejeune@kodak.com>
>Cc: <samba@lists.samba.org>
>Sent: Tuesday, October 05, 2004 12:14 PM
>Subject: Re: [Samba] random errors"the local drive name is already in
use.
>This connection has not beenrestored."
>
>
>  
>
>>I have had this problem unrelated to samba. I believe it is in the login
>>    
>>
>scripts. Perhaps you are using the "net use /persistent" switch
when you do
>no need to?
>  
>
>>Regards,
>>
>>Gerald Bird
>>
>>----- Original Message -----
>>From: yves.lejeune@kodak.com
>>Date: Tuesday, October 5, 2004 11:05 am
>>Subject: [Samba] random errors "the local drive name is already in
use.
>>    
>>
>This connection has not been restored."
>  
>
>>>Hello,
>>>
>>>I have random errors that I can not analyze nor fix:
>>>when several users connect to the same Samba share, they get
>>>sometimes
>>>error messages
>>>"the local drive name is already in use. This connection has
not
>>>been
>>>restored", although the connection
>>>is still usable afterwards.
>>>      
>>>
>>
>>    
>>
>
>  
>

Thanks for your suggestions.

Unfortunately, my warning messages do not happen at login time.
> "Hamish" <captainmish@gmx.net> wrote:
> 
> I had the same problem with XP.
> Modifying the login script to delete the mapping first was the only cure 
I found.
> 
> and just recently I found Service Pack 2 fixes this in XP!
> 
> I don't know how the other OSs might be affected.
> 
> Steve
> Gerald Bird <rocknrollgolfer@shaw.ca>@INTERNET wrote:
> 
> I have had this problem unrelated to samba. I believe it is in the login 
scripts. Perhaps you are using the "net use /persistent" switch when
you
do no need to?
> 
> Regards,
> Brad Otto <bottojr@myrealbox.com> wrote:
> I think this is possibly a windows problem, I have had the same error in 
> high usage workgroup situations with win2000. There is a relatively 
> simple fix, I think if you search MS for the error message it is there.
> H
> 
> Brad Otto wrote:
> 
> >Try using:
> >
> >net use * /delete /yes
> >
> >Before mapping any drives in the login script.  This will clear any 
drives
> >already mapped.  I do this in my login script to get rid of the drives 
that
> >XP/2k will sometimes hold on to and not let go on reboot.

(Sorry for the first incomplete answer, here is the long version)

Thanks for your suggestions.

Unfortunately, my warning messages do not happen at login time.
They happen during the use of the share, and in most cases the persistent 
option was not set.

I have checked the "idle time before disconnecting" option in the
security
settings: it is set to 0,
as recommended on some Windows help sites..

I have checked MS known problems, and found a few ones which are supposed 
to be fixed in Windows 2000 SP 3.
Something strange is that they mention the same error message with the 
"device" word instead of "drive".
Other problems refer to anti-virus tools, e.g. VirusScan: I have it but do 
not think it is involved, because I have a version number
higher that the one which is supposed to fix the bug, and I have disabled 
the scan of network drives,
and test PC do not have it.

My current conclusion is that the error message is just an alias for the 
"normal" disconnection popup.
So I just have to find why I get disconnections...

Would you be aware of temporary disconnection caused by network timeouts ?
And were to tune the timers ? I could not find any parameter at Windows 
level.

Best Regards,
Yves Lejeune.

> "Hamish" <captainmish@gmx.net> wrote:
> 
> I had the same problem with XP.
> Modifying the login script to delete the mapping first was the only cure 
I found.
> 
> and just recently I found Service Pack 2 fixes this in XP!
> 
> I don't know how the other OSs might be affected.
> 
> Steve
> Gerald Bird <rocknrollgolfer@shaw.ca>@INTERNET wrote:
> 
> I have had this problem unrelated to samba. I believe it is in the login 
scripts. Perhaps you are using the "net use /persistent" switch when
you
do no need to?
> 
> Regards,
> Brad Otto <bottojr@myrealbox.com> wrote:
> I think this is possibly a windows problem, I have had the same error in 
> high usage workgroup situations with win2000. There is a relatively 
> simple fix, I think if you search MS for the error message it is there.
> H
> 
> Brad Otto wrote:
> 
> >Try using:
> >
> >net use * /delete /yes
> >
> >Before mapping any drives in the login script.  This will clear any 
drives
> >already mapped.  I do this in my login script to get rid of the drives 
that
> >XP/2k will sometimes hold on to and not let go on reboot.