Blog Posts tagged with Kace Samba Shares

Ask a question

Unable to access Samba share on KACE appliance using hostname

I noticed recently that I was no longer able to access the KACE share files using the hostname, even though DNS was working properly.  I could only access it using the IP address of the KACE appliance.  The result of this was that I was no longer able to deploy clients using the KACE appliance.  All clients would have to be deployed using group policy or manually.  I contacted Dell KACE support and after many days of waiting for a response, the tech told me that as long as I had a workaround, they were not going to pursue a solution further.  Well today, I discovered that the problem is worse than just not being able to deploy, it also means that I cannot update any clients.  Faced with the prospect of manually updating many client machines, I had new incentive to try to find a solution again.

I looked online for information about Samba and hostname restrictions, and found that hostnames need to be less than fifteen characters.  My hostname is 14 characters formatted like this xx-xx-xxxx####.  I also noticed that others online where having the exact same symptoms with hostnames and Samba shares even without KACE being involved, in that they could only access the shares if they used the IP address and not the hostname.  So, I took a chance and changed my hostname, so that is was formatted like this xx-xx-xxxx.  And, after a reboot, I could then access the KACE shares using just the hostname.  Victory!!!  Just for fun, I changed the hostname back to what it was originally, and then the shares become unavailable using the hostname again.  So, I've gone with the shorter hostname and all seems to be working well again.

I am sharing this with all of you in case you have experienced the same issue.  Try changing your hostname.  It may help.
View comments (7)

K1000 and K2000 SAMBA remote code execution vulnerability

According to a Nexpose scan, both our K1000 and K2000 show as vulnerable to the following SAMBA bulletin.
I have not seen anything from Quest regarding this.

== Subject:     Remote code execution from a writable share.
== CVE ID#:     CVE-2017-7494
== Versions:    All versions of Samba from 3.5.0 onwards.
== Summary:     Malicious clients can upload and cause the smbd server
==              to execute a shared library from a writable share.


All versions of Samba from 3.5.0 onwards are vulnerable to a remote
code execution vulnerability, allowing a malicious client to upload a
shared library to a writable share, and then cause the server to load
and execute it.

Patch Availability

A patch addressing this defect has been posted to


Additionally, Samba 4.6.4, 4.5.10 and 4.4.14 have been issued as
security releases to correct the defect. Patches against older Samba
versions are available at http://samba.org/samba/patches/. Samba
vendors and administrators running affected versions are advised to
upgrade or apply the patch as soon as possible.


Add the parameter:

nt pipe support = no

to the [global] section of your smb.conf and restart smbd. This
prevents clients from accessing any named pipe endpoints. Note this
can disable some expected functionality for Windows clients.


This problem was found by steelo <knownsteelo@gmail.com>. Volker
Lendecke of SerNet and the Samba Team provided the fix.

View comments (2)
Showing 1 - 2 of 2 results

Top Contributors

Talk About Patch Management