Error Unable To Mount Kbox Share At
Contents |
helpful is this to you? Average Rating 3 3760 views 03/10/2015 Dell KACE K2000 Deployment Appliance KACE Product Support KACE Boot Environment unable to mount kbox share error 1231 (KBE) KBE kbe (Kbox boot environment) I created a KBE image have unable to mount kbox share error 53 downloaded all the drivers packs 3,4,5 recache to drivers and am still getting this error any thoughts? Answer k2000 unable to determine server ip address Summary: TextSave summary Cancel 0 Comments [ + ] Show Comments Comments Please log in to comment Community Chosen Answer 1 Just testing my 9020 and it works
Kbe 111717
with pe 3 and 5 x86 kbe pxe boot. Could be extra drivers in the kbe causing the problem. Copy the directories from \\ikbox\drivers\kbe_windows_x86 to your tech station and delete all the sub dirs from the kbox.then go to http://www.dell.com/support/home/us/en/04/product-support/servicetag/2J1Y942/drivers and download the cab file for the"Dell Command | Deploy WinPE 3.0 Driver Pack" located under systems management drop-down, expand k2000 rebuild boot environment it using 7zip and copy those folders to the \\ikbox\drivers\kbe_windows_x86 area and build a new kbe and boot to that one Answered 03/11/2015 by: SMal.tmcc Please log in to comment gerroe 1 year ago This idea fixed it!! thanks!!! I believe the extra drivers were causing the issue, i removed the extra drivers and was able to get it to work, thanks for all the help! WOOT!! SMal.tmcc 1 year ago the video problem was what made me think it was extra "bad" drivers. I have never seen any video problems in the pe mode Please log in to comment Answers 0 Can you give more detail on type of system and NIC? When you download the drivers needed for your nic copy it to either \\ikbox\drivers\kbe_windows_x64\SomeSubDirectory or \\ikbox\drivers\kbe_windows_x86\SomeSubDirectory. I create a directory with company name and then create dirs under that for each type of nic (for ex: \\ikbox\drivers\kbe_windows_x64\tmcc\pro1000x64). Copy all the files not just the cat,inf, & sys. the din and dll files are also needed a lot of the times. Once you have the f
How helpful is this to you? Average Rating 4 7117 views 11/22/2012 KACE Product Support Systems Deployment Very odd issue, we have a perfectly working k2000 KBE that will image fine when inside of our firewall, create k2000 boot environment in one of our regional offices we have been unable to do this so
Kbe Driver Pack
far, we have muddle through to the stage where its getting an IP address and then attempting to launch the KBE,
Kbe Manipulator
but when getting ot the ***Mounting the KBOX install shares we get: System error 67 has occurred. The network name was not found ERROR: Unable to mKBOX share at \\â””¿Ë¾Y\peinst (and yes its with http://www.itninja.com/question/system-error-1231-unable-to-mount-kbox-share-at-ip-address those odd characters) on our firewall we see nothing hitting it to indicate a port being blocked. and after it fails i can get an IP address and can ping the IP and hostname of our K2000. None of this happens from inside our main office, so the system seems to be working perfectly, i was wondering if anyone had any ideas on this - we are doing this on a http://www.itninja.com/question/k2000-kbe-giving-unable-to-mount-kbox-share-at-e-y-peinst CISCO 1841 DHCP config on this is as follows to get us this far: ip dhcp pool Test-WAN network 172.30.10.0 255.255.255.0 bootfile kbox2000.0 next-server 192.168.28.89 domain-name ourdomain.com default-router 172.30.10.1 dns-server 192.168.21.10 192.168.21.11 option 66 ip 192.168.28.89 (our k2000 ip) any thoughts would be really appriciated. Answer Summary: TextSave summary Cancel 0 Comments [ + ] Show Comments Comments Please log in to comment Answers 1 Hi Trentderby, Can you manually mount the PEINST share? When it fails, type this command: net use \\%K2000_IP%\peinst Y: If it mounts, try browsing to Y: and see if it you can access the contents. Also what version if your K2000 running? Answered 11/22/2012 by: ruanben Please log in to comment ruanben 3 years ago Also , if you're on 3.4 , make sure your driver share password does not include any special characters. eg. ?/#@ . If thats the case, you'll have to change the driver share password in the K2000 , build a new KBE with the new password in it, and replicate this KBE over to the RSA. trentderby 3 years ago ah, im on 3.4 and the password does have an ! in it. ill change this now. trentderby 3 years a
you? Average Rating 3 5714 views 08/13/2013 Dell KACE K2000 Deployment Appliance KACE Product Support When running 1st Scripted install, I get "Mounting the KBOX install shares - System error 86 has occurred. - The specified password is not correct. Error: Unable to mount KBOX share http://www.itninja.com/question/when-running-1st-scripted-install-i-get-mounting-the-kbox-install-shares-system-error-86-has-occurred-the-specified-password-is-not-correct-error-unable-to-mount-kbox-share-at-10-128-20-118-peinst at \\10.128.20.118\peinst" The path it tries to map seems to be a hidden share on the http://www.itninja.com/question/why-can-t-i-boot-to-the-k2000-anymore-from-my-boot-environment-on-my-flash-drive K2100 box. If I try to go directly to the "peinst" share, it doesn't ask for credentials. It just denies access. Is this something that got missed when setting up the box. This is the 1st attempt to do a scripted install. The source media and scripted install were just created as it did the same thing with the one created when we did unable to quickstart training with a KACE technician. Answer Summary: TextSave summary Cancel 0 Comments [ + ] Show Comments Comments Please log in to comment Answers 0 It's a hidden share but you should be prompted for a login. Have you changed the samba password? If so, you need to rebuild the KBE so it uses the new password. Answered 08/13/2013 by: nheyne Please log in to comment MNBobster 3 years ago Something weird is going on. "peinstall" allows me unable to mount to open it now without a login dialogue. It is hidden, but accessible. We have not changed the Samba password since the quickstart. nheyne 3 years ago Maybe you had a cached password that was incorrect? Sounds strange. Please log in to comment 0 Same error happened to us during the jump start training and the Dell trainer was shaking his head. We updated our server version and all of a sudden the KBE would not load with the same error above. We had to download the newest copy of Media Manager and recreate the KBE. The samba share password never changed during that time. Not sure if its the same issue you're having.... Answered 08/13/2013 by: timw77 Please log in to comment MNBobster 3 years ago last edited 3 years ago I downloaded Media Manager from the K2000, which is the latest revision. Did you get it elsewhere? MNBobster 3 years ago last edited 3 years ago I am pretty sure it is because the KACE is not allowing me to link Scripted Installs to my created KBEs. It only will link to the ones that came with the box. I am currently awaiting KACE to call me. timw77 3 years ago I wanted to say that it was a download from their support site, but I can't find it anywhere except the KBOX. We tried everything. Uploading new source media, re hard-coding the Samba share p
on my flash drive? tsienkiewicz@ldirx.com How helpful is this to you? Average Rating 4 5507 views 10/01/2013 Dell KACE K2000 Deployment Appliance KACE Product Support K2000 post-imaging KACE Boot Environment (KBE) I have a flash drive that I have been using to boot to my K2000 so I can do Imaging and Scripted Installs. I am not able to boot to it anymore. The only thing that we changed is at my desk, we had to put a new IP address range and new subnet on the port I am using. I am just trying to figure out what is causing me not to boot into the K2000 anymore. These are the errors I am getting: ERROR: Unable to determine server IP address from DHCP WARNING: Using hardcoded K2000 IP address as fallback System error 53 has occured ERROR: Unable to mount KBOX share at \\192.168.0.10\peinst 0 Comments [ + ] Show Comments Comments Please log in to comment Answers 0 did you add the dhcp options to this new subnet? Answered 10/01/2013 by: SMal.tmcc Please log in to comment Please log in to comment 0 Yes Answered 10/01/2013 by: tsienkiewicz@ldirx.com Please log in to comment nheyne 3 years ago Can you authenticate to \\k2\peinst on your workstation? Also, what is the reason you're using a usb key and not dhcp to boot to the K2? Please log in to comment 0 This is typically a DHCP issue. As an alternative, you can use KBE Manipulator to build a static ip KBE (points directly to your K2 instead of using DCHP) and then put that to a usb key. CoreyLead L3 Enterprise Solutions Consultant, K2000If my response was helpful, please rate it! Answered 10/01/2013 by: cserrins Please log in to comment Please log in to comment 0 This worked great. Thank you very much. Answered 10/01/2013 by: tsienkiewicz@ldirx.com Please log in to comment Please log in to comment -1 Where do I find the KBE Manipulator? Answered 10/01/2013 by: tsienkie