/build/static/layout/Breadcrumb_cap_w.png

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.

Comments

  • Update: if you have KACE connected to your domain, then you will need to rejoin the server to the domain after changing the hostname. - dean.allmann 9 years ago
  • This is a very annoying problem to have. The location that provisioning is looking for the files exists, but the path it's trying use cannot get there.
    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
  • I wish I had a better update for you. This was working fine when I posted this blog, but after I got your comment, I tested it again and now it is back to not working. I can still access the files by IP address, but not by hostname. So, I supposes it is back to the drawing board, and hope that Dell comes up with a permanent fix to this issue. - dean.allmann 9 years ago
    • Just a few minutes ago the hostname worked for me after I had unjoined from the domain for SSO.
      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
      • Thanks for your comments. I would not have connected SSO/Domain Joining with this issue, but now that you mention it, I bet ours stopped working when I rejoined the domain as well. - dean.allmann 9 years ago
  • I have bad news as well. This time when I unjoined the domain this time it didn't make a difference. I was unable to use the hostname to connect. I'm finding that there are lots of posts on here of people with the exact identical problem, but most of them are from a few versions ago. They keep repeating changing settings in UAC on the machine, but we have UAC turned off on our test machine. Not sure what to do next. - AFCUjstrick 9 years ago
    • Did you remove the computer object from AD? I'm testing that now. Don't know if it will work, but I'm hopeful. - dean.allmann 9 years ago
  • We did not. Good luck to you. - AFCUjstrick 9 years ago
    • Well, when I looked in AD, the computer and user objects had already been removed, so the KACE system must have deleted them as part of the unjoining. The good news is that now I'm able to access the shares again using the hostname. So, I recommend checking your AD to be sure that the computer and user objects it created when joining are gone. - dean.allmann 9 years ago
  • Just got this from support. It's brilliant!
    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 8 years ago
    • Thank you!!! I am very grateful to finally have an answer that works. - sbaitsell 8 years ago
  • Hi,

    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 8 years ago
This post is locked

Don't be a Stranger!

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

Sign up! or login
Blog

View More Blogs from dean.allmann

Share

 
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