KACE: Can't access Kace samba share by \\servername but I can \\IP
The server is in DNS both A and PTR, it is resolving from the client pc using ping servername. I cant access the server by typing \\servername but I can access it \\IP.
On Windows XP both \\servername and \\ip seams to work. but windows 7 i have this issue with 90% off all our client.
I have tried with FQDN \\kbox.server.com
Any idea what it might be?
17 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
davik2001
8 years ago
This is a common problem - the culprit is the length of your FQDN for your KACE appliance. Get it to be under 15 characters and that will most likely fix the problem.
Comments:
-
Hello,
I have tested with a short FQDN, and it's work fine ... but the problem is that our client has a FQDN much longer ... we still only one character !
Are there another solution ?
Thanks - Tazmax 8 years ago-
Can you do IP? - davik2001 8 years ago
-
I was thinking if you could just use strictly the IP but my guess that isn't an option. Does the customer have an internal DNS server? What about sending a script out to the users' systems which will modify their local host file? - davik2001 8 years ago
-
Thé costumer have a DNS server ans thé kbox is in
.we have already tried to put IP in the Host file, but without success. the problem comes from the Samba share .
From desktop, ping the name and IP works very well , samba shares over IP as well. is sharing the name the name or FQDN that does not work. I have tester with Windows 7, 8, 8.1 (with à VM XP work good !!)
UAC and Firewall down of all desktop.
With or not antivirus - Tazmax 8 years ago
-
If the customer has a DNS server, why not just give the kbox a shorter system name? - davik2001 8 years ago
-
Hello Davik2001 ,
The customer's domain name is part of a subdomain , which gives us kboxname.subdomain.domain.lan when you add up all of the FQDN , it only remains one character for KBOXNAME.
Thanks - Tazmax 8 years ago
This is a known bug. K1-14096
You may be able to access the samba share with win 7 using the ip address instead of hostname. Please try.
Also take your account and try the following; Domain users can still browse to the KBOX shares if the Domain Admin goes into ADUC, opens the properties of the user and selects "Use Kerberos DES encryption types for this account" under the Account tab.
Users should still be able to access all other network shares with this change.
Another option would be to default vastool to use AES encryption which is turned on by default but this would likely cause problems for Windows XP and earlier version since they don't support AES out of the box.
Those are listed as work around options;
The bug will be fixed in version 6 coming out in March 2014. - nshah 10 years ago
May I ask what version you are on and if you had SSO enabled prior to any upgrades? - KACE_Mary 8 years ago