We have an issue where smbclient is intermittently hanging. It then proceeds to chew up huge amounts of cpu and in one case so far, has caused a unix sever to crash & reboot.
This has happened a handful of times on different UNIX servers trying to smbclient to different windows servers. The only common theme is it appears to happen at roughly the same time and the smbclient is running on Solaris 10 UNIX servers that reside in the same LDAP/KDC domain & are trying to authenticate to a different LDAP/active directory windows domain.
I tried to run truss, but given the process hung some time ago, it provided no output.
If I run the smbclient now, it works fine most of the time, the issue only pops up every couple of weeks.
This is very difficult to try & troubleshoot as smbclient doesn’t appear to generate any logs ( that I'm aware of). I noticed on a samba faq that smbclient has been known to hang when used with the –c flag. Have you seen this in the past?
Can you test this with the latest 3.5.4 smbclient please ?
Is there a specific bug that you are aware of that this issue may relate to? Is it possible that there may be a fix for the version that I'm running? The resaon I ask is the company I work work will not allow me to download samba 3.5.4, there is a process where our engineering team need to test and pkg freeware before allowing us to deploy it into the environment.
If you need specific support for 3.2.15, please refer to
There are companies listed with Samba skills that can help you with releases that are not supported anymore by the Samba Team. This kind of problem might be a bit difficult to analyze completely without access to such a box, so you might better pay someone to get a timely response or who can sign an NDA to log in to your net.
smbclient != libsmbclient. Correcting component.