Unable to mount KBOX Share

Any reason why I randomly start getting this error when booting into the KBE 3? I say random as it works fine for for days and then I start getting this error for no reason.
  • No changes to the KBE or hardware.
  • Same PC everytime as I have been using it for testing.
  • I can login using a Win10 KBE on the same PC fine.
  • At the error prompt I can map the drives manually using the commands from the startnet.cmd file. This eliminates network and credential issues.
  • I can login using a VM to the KBE 3.

Any ideas?

4 Comments   [ + ] Show comments
  • I generally blame the network when it happens. - chucksteel 3 years ago
  • I have found that it seems to be a timing issue. If the mount comes before the network actually settles, the share will fail. - jboling 3 years ago
  • Mmmm OK. Can anyone actually tell me what "Waiting for network devices to settle" means? What is the script waiting for exactly. - JLMCC 3 years ago
  • We will get Mount KBOX errors randomly on any of the KBEs and we found we have to restart the K2000 server and they seem to work fine for another week or so. However, I believe our problem is overloading the server. We will image dozens of PCs a day at times and it seems to give trouble when we have many PCs imaging at the same time. - DaveMT 3 years ago

Answers (1)

Posted by: cregan 3 years ago
White Belt
I had this issue too. Simply rerunning startnet.cmd was enough to get it to perform a run-through but subsequent reruns would also fail. Rebooting the appliance resolved the issue for me.

Don't be a Stranger!

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

Sign up! or login


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