Unable to access Samba share on KACE appliance using hostname
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.
Our hostname is only 4 characters, but the path keeps trying to use the fully qualified name which puts it over 14. Any thoughts as to how to correct this other than what you posted earlier? - AFCUjstrick 9 years ago
Once I joined the domain again and restarted the K!000 the hostname stopped working. This has to be a big of some kind. - AFCUjstrick 9 years ago
The best solution to this issue is to install the agent with the IP not the name of the K1000. To do this, please go to SETTING + Provisioning + Provision Agent. Fill out the page normally but at the bottom of the page in the “Alternate Download Location” box please add the IP address of your K1000. Push out the agent install as normal and that should fix the issue.
Please let me know if you have any issue with the above steps - AFCUjstrick 9 years ago
This is a known issue after enabling SSO.
The original KB Article:
https://support.software.dell.com/k1000-systems-management-appliance/kb/125812
The updated KB Article referencing the ALT Location option in 6.3:
https://support.software.dell.com/k1000-systems-management-appliance/kb/148570
My understanding it's caused by the K1000 using DES encryption which is disabled by default in Vista and above. - theatrebyte 9 years ago