Paul,

I'm using TCPware. What stack are you using?

The reason I ask is that I also caused the CIFS product to lockup but
this happened as a result of my fooling around with the Samba shutdown
scripts.

I had been doing this:
NETCU remove service 139 tcp

When I should have been doing this:
NETCU remove service/abort 139 bg_tcp

Things got so messed up that the only way to recover was to restart
TCPware (something I never usually need to do).


Neil Rieck
ICSIS/Trinity Development
Bell-ATS (Advanced Technical Services)
Bell Canada
20 Water St. N.,
Kitchener, Ontario,
Canada. N2H-5A5
519-571-6303

> -----Original Message-----
> From: paul.beaudoin@hsbc.com [mailtoaul.beaudoin@hsbc.com]
> Sent: Thursday, September 28, 2006 10:24 AM
> To: Rieck, Neil (N123119)
> Subject: RE: New Version of CIFS (Samba)
>
> Niel
>
> FYI - I have posted this the CIFS site ....
>
> Regards
>
> Paul
>
>
> I broke it. CIFS was steaming along fine and I was trying various

things to
> measure performance/abilities etc. when it stopped and I can't

reconnect;
> The exact sequence is this:
>
> I copied a large (250mb) zip file originally made on the PC and

copied to
> VMS some time ago to the directory served out. I then could see it

from the
> PC and started to unzip it. This ran slowly for about 10 min and while

it
> was running I watched the net/systems and noted 2 'facts': The 11mb
> wireless network was never utilised more than 12-13% and the VMS box

was
> doing high (peaking up to 1300 ) buffered io. I though it might help

to
> increase bytlm on the accounts and raised in on samba$nmbd and

samba$smbd
> accounts from 32768 to 65536. shortly thereafter the vms-pc

connection
> failed complaining the connection was lost.
> Taking this opportunity, I restarted CIFS to activate the new quotas

but
> the pc would not reconnect saying the server was unavailable and
> 'insufficient resources exist' (or similar). I assumed the pc to be at
> fault and rebooted it. No change. I then booted up another pc which

had
> been connected/disconnected a few time successfully but it got the

same
> error. This led me back to VMS. I reverted both accounts back to bytlm

=
> 32768 and restarted samba. No change. I found the individual log files
> (interesting naming convention here - looks like filetype and filename

are
> reversed) and it shows this entry for each connection attempt:
>
> [2006/09/27 18:06:48, 0] SAMBA$BUILD:[000000.tdb]tdbutil.C;1732)
> tdb(/SAMBA_ROOT/VAR/LOCKS/connections.tdb): tdb_oob len 49176 beyond
> eof at 49152
> [2006/09/27 18:06:48, 0] SAMBA$BUILD:[000000.smbd]connection.C;1195)
> claim_connection: tdb_store failed with error IO Error.
> [2006/09/27 18:06:49, 0] SAMBA$BUILD:[000000.tdb]tdbutil.C;1732)
> tdb(/SAMBA_ROOT/VAR/LOCKS/connections.tdb): tdb_oob len 49176 beyond
> eof at 49152
> [2006/09/27 18:06:49, 0] SAMBA$BUILD:[000000.smbd]connection.C;1195)
> claim_connection: tdb_store failed with error IO Error.
> [2006/09/27 18:06:49, 1] SAMBA$BUILD:[000000.smbd]service.C;1543)
> too many connections - rejected
> [2006/09/27 18:06:50, 0] SAMBA$BUILD:[000000.tdb]tdbutil.C;1732)
> tdb(/SAMBA_ROOT/VAR/LOCKS/connections.tdb): tdb_oob len 49176 beyond
> eof at 49152
> [2006/09/27 18:06:50, 0] SAMBA$BUILD:[000000.smbd]connection.C;1195)
> claim_connection: tdb_store failed with error IO Error.
> [2006/09/27 18:06:50, 0] SAMBA$BUILD:[000000.tdb]tdbutil.C;1732)
> tdb(/SAMBA_ROOT/VAR/LOCKS/connections.tdb): tdb_oob len 49176 beyond
> eof at 49152
> [2006/09/27 18:06:50, 0] SAMBA$BUILD:[000000.smbd]connection.C;1195)
> claim_connection: tdb_store failed with error IO Error.
> [2006/09/27 18:06:50, 1] SAMBA$BUILD:[000000.smbd]service.C;1543)
> too many connections - rejected
>
> It seems to be having problems accessing the passdb.tdb file (if I

read
> this right) so I tried removing the entry for the account I was using

and
> re-writting it. No change. I'll try renaming the file and restart CIFS

as I
> think this is where it is created if it doesn't exist. there are only

2
> accounts so no problem to re-enter them.
>
> If you want to track this problem and there is anything else you need,
> please let me know. Alternatively, if you know about this problem, can

you
> let me know the fix?
>
> Many thanks
>
> Paul
>
> ************************************************** **********
> HSBC Bank plc
> Registered Office: 8 Canada Square, London E14 5HQ
> Registered in England - Number 14259
> Authorised and regulated by the Financial Services Authority
> ************************************************** **********
>
>
> -----------------------------------------
> SAVE PAPER - THINK BEFORE YOU PRINT!
>
> This E-mail is confidential.
>
> It may also be legally privileged. If you are not the addressee you

may
> not copy, forward, disclose or use any part of it. If you have

received
> this message in error, please delete it and all copies from your

system
> and notify the sender immediately by return E-mail.
>
> Internet communications cannot be guaranteed to be timely secure,

error
> or virus-free. The sender does not accept liability for any errors or
> omissions.