can't browse with windows explorer to hostname since upgrade to 6.0
I just updated to 6.0.101863 a couple of days ago. Since then, I can't browse to the host name by going \\kace1000. If I use the IP address, it works fine. I can put the host name in a web browser and get to the GUI no problem. This seems to be causing some issues, such as when I try to deploy the agent - "Tye system cannot find the file specified" when it tries to look in "//kace1000/client.....". I can ping kace1000 and get a reply with the correct IP address.
Answers (4)
Is the samba settings enabled? Go to Settings > Security > "Enable file sharing" . Perhaps it's been unticked in the update?
Comments:
-
Yes, it is enabled. I've seen this happen before (not on K1000 though) when the time hasn't been set correctly. However, the time on the K1000 and the desktops is exactly the same in this case. - gcoolong 9 years ago
Can you check your DNS settings to see if there are 2 records for your KACE box IP address please? Found that we had a DNS record for the original kace box host name, and one for the hostname we changed it too. This hasn't affected anything else except from this.
Hopefully that makes sense.
Comments:
-
I only have one DNS record for it - the name that I changed it to when I first got it a few years ago and that's been working right along. - gcoolong 9 years ago
Check this kb article out:
http://www.kace.com/support/resources/kb/solutiondetail?sol=125812
Comments:
-
but this also affected the 5.5 - Nico_K 9 years ago
I'm struggling with the same problem myself. In addition to being unable to browse the Samba share w/ the hostname, we are unable to manually provision the agent through the K1000.
I've had a case open with Dell support for about a week and a half now, and have been shuffled around to about 4 techs and the most that we've discovered is that you can browse the share by enabling Kerberos DES encryption for the user account in AD. Not really a fix, considering that doing this causes issues with other apps in our environment. This also did not resolve the problem with us being unable to perform manual provisioning.