/build/static/layout/Breadcrumb_cap_w.png

Since most recent Kbox service patch older KBE isn't working

A little over a month ago I applied the most recent service patch/update from Dell to our K2000. The current version shown is 3.5.80613 though I am unsure as to what the previous version was, maybe 3.5.xx or possibly 3.4.xx. Now an older KBE for CF-29 Panasonic Toughbooks isn't working which had been created in most likely 3.3.xx. I am receiving the "Cannot mount kbox share" error as if the password were bad, or drivers were missing, but the KBE worked prior to the update.

I've read several places where folks said that the KBE needed to be created using the same version Media Manager as the KBox version. Is there a way to bring this KBE back to snuff and get it rolling again? 


0 Comments   [ + ] Show comments

Answers (2)

Posted by: cserrins 10 years ago
Red Belt
2

When you get to the command prompt, type in ipconfig.  If nothing is listed, then it is definitely a network driver issue.

Otherwise, check your samba share password and make sure it is correct.

Corey
Lead L3 Enterprise Solutions Consultant, K2000
If my response was helpful, please rate it!

Posted by: nheyne 10 years ago
Red Belt
0

Yep, rebuild it with the updated Media Manager.


Comments:
  • I'm assuming you talking about simply building a new one from scratch, which I've tried and its still not working. If I remember correctly, this one was a pain in the butt because we had to remove ALL other drivers from the \drivers folder and create the KBE with only the handful of drivers specific to the model. If that's what I've got to do then so be it, but I was hoping there might be a much more simple choice. - aaronr 10 years ago
    • If you place the needed network driver along with the others at \\k2\drivers\kbe_windows_x64, the new KBE should pick it up. - nheyne 10 years ago
    • If you're dealing with a driver that doesn't play well with others, then unfortunately that's the method you'll have to follow in order to get a working KBE. Before you go through all of the trouble, if you have a USB drive and a Toughbook within striking distance you can try this simple test:

      1.) Discern what network card the Toughbook has an obtain Win7 drivers for it. Unpack/unzip them so you have the .inf and associated files.
      2.) Copy those files to a USB drive
      3.) Boot the Toughbook into KBE and wait for it to fail.
      4.) Run the command "drvload inf_path" where inf_path is the path to the driver inf on the USB drive.
      5.) Once the command completes, run "startnet.cmd" and see if KBE can mount the Samba shared.

      If it works, then you can add the driver from the USB drive to \\k2000\drivers\kbe_windows_x??\ and recache, rebuild. - mpace 10 years ago
      • mpace, that's great! Thank you! I'm having to go through the strenuous process anyway and find drivers for multiple CF29 hardware revisions. This is the one time I use the driver harvest utility but I'm definitely keeping your walkthrough saved for future troubleshooting. Again thank you! - aaronr 10 years ago
 
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