Kace unable to mount kbox share
Hi everyone,
after creating countless KBEs and inserting numerous drivers and removing them again,... i finally give up.
Situation is this:
Computers, we try to install with Kace (K2000) sometimes, (really only sometimes) can't connect to the Kace.
We just fixed the well known error "rpc_upload_invemntory" (quest forum) by creating a new KBE (again)
Everything was fine, coworkers install computer with wd19dcs - they did not get network connection, so I inserted the drivers from the Dell website - created a new KBE and all computers got connection and also got installed.
Thus having experienced strange behavior, we double checked by trying to re-install those computers again and tadaa,...
we got the "cannot connect to kbox... "-error
After removing the docking from one of those system, and connecting directly to the device's lan port worked.
Putting it together We have this situation:
Sometimes computer connect to the kbox, sometimes they don't, sometimes they work with a dockingstation, sometimes not, but they do, when using the internal lan-port.
Network-switch was already resetted, Dockingstations were resetted. Kace was rebooted.
We can't reproduce the situation, because it is possible, that a system we just set up, won't work in a second try.
I am really going mad.
Does anyone have an Idea?
I would apreciate any hints or tipps, or whatever
thank you
Michael
Answers (2)
We have exactly the same problem, it can even be reproduced, regardless of whether it is connected to a docking station or not. Computer is started with PXE. If everything goes well, you are then in the menu. There you select reboot system and tada, the network drives are not connected at the next start. If you now enter startnet, sometimes several times, the device connects the drives and you are back in the menu and can install
I was getting the "can't connect to KBOX error" when trying to image a pc. After poking around, I found that the Boot Manager password/username was somehow changed. I reset it to what it should be, and I was then able to image without any errors. I know this is not quite the same issue you are having, but figured I would pass it along. Good luck.