Unable to connect to Samba share clientdrop. Multiple sessions connected.

It appears I am not able to connect to samba share for clientdrop.

Did a map drive by host and IP and both got denied indicating bad password.  The password is correct since another person was able to connect.

I don't  wish to reboot the K1000 since this will take down production.

One error that did show up in the attempt is something about multiple connections from diff sources at same time.

How do I go about locating the sessions and terminating it?  I think there is a way through terminal.

2 Comments   [ + ] Show comments
  • I would check the saved passwords (netplwiz) and delete the saved credentials for K2000. - CarstenBuscher 1 year ago
  • No cached password been saved on the computer that I used to attempt to connect to.
    As far as the other sessions connected I have no info on where it came from.
    I need a way to disconnect the open session connection without rebooting the K1000. - mikehuang00 1 year ago

Answers (1)

Answer Summary:
Posted by: Channeler 1 year ago
Red Belt


Make sure you don't have existing cached connections in your Windows OS (net use /delete \\KACE-SMA-IP), do this before attempting to connect again.

To restart the samba service, go to Settings > Security Settings (Scroll down), click Save and Restart Services.
This could make the box inaccessible for two or four minutes.

That will restart the SMB service, liberating existing lock files.---->

That's the Samba Service locking behavior... probably causing that,

NOTE: A file can be a folder as well.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ