New Lenovo's Wont Connect
-
cjones34
- How helpful is this to you?
- Average Rating 0
- 4754 views
- 05/04/2011
Hey guys, I have two test Lenovo's, one is a T420s and one is a X220. Both of them get an error on "Locating KBOX IP address from DHCP option 66 or 244", "ERROR: Unable to determine KBOX IP address" the problem is that I have other Lenovo's and Dell's connecting just fine through that same port, and I have no other connection problems anywhere on campus with any other machines. I have used the double driver to extract the drivers from the machines and load them to the KBOX in both the KBE and the windows 7 driver folders and recached. I also wiped the proprietary stuff from the machines and have just Windows on there. Any other suggestion, or am I missing something?
0 Comments
[ - ] Hide Comments
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
Answer this question
or Comment on this question for clarity
Answers
its definitely a network driver issue, i had to add drivers to my kace driver folder for it to recognize a few hp machines.
Please log in to comment
cjones34,
If you do an IP config at the command prompt, do you have an IP Address? If not this is a driver issue. You will need to download the win 7 driver for this and put in the driver share. The Kace Driver Pack includes the latest drivers so that should work as well.
Since KBE, you not only have to recache your drivers from the webui, but you must build a new KBE after recaching so that you have a KBE that has theose new drivers.
Corey
If you do an IP config at the command prompt, do you have an IP Address? If not this is a driver issue. You will need to download the win 7 driver for this and put in the driver share. The Kace Driver Pack includes the latest drivers so that should work as well.
Since KBE, you not only have to recache your drivers from the webui, but you must build a new KBE after recaching so that you have a KBE that has theose new drivers.
Corey
Please log in to comment
Thanks that was deffantly it, I reloaded the KBE and it worked fine.
One other question though, when I reloaded the KBE it shows up in a seperate list when booting into the KBOX does that have to stay there or is there a way to get that to be the only KBE in the list?
One other question though, when I reloaded the KBE it shows up in a seperate list when booting into the KBOX does that have to stay there or is there a way to get that to be the only KBE in the list?
Please log in to comment
If you go to
settings -> general settings -> default KBE
Once the new KBE is the default you can delete the old ones.
settings -> general settings -> default KBE
Once the new KBE is the default you can delete the old ones.
Please log in to comment
Exactly, or you can keep the old ones if you like. Some will have a kbe with no added drivers for older machines, this requires less memory. Remember your default KBE is always called Windows Deployment and Recovery.
Don't forget too, that if you delete the boot environment, you can also go to Library and then Source Media to delete the same, if you want. Or keep it in case you want to build a new kbe built off that source media.
Don't forget too, that if you delete the boot environment, you can also go to Library and then Source Media to delete the same, if you want. Or keep it in case you want to build a new kbe built off that source media.
Please log in to comment
@cjones 34 - Which nic drivers did you add? I added the ones from Lenovo's site and still can't get the T420s to start imaging. I have the T410s booting and imaging fine, but can't get the T420s to work.
Please log in to comment
I have these two in my KBE, intel(r) 82579lm gigabit network connection and intel(r) centrino(r) advanced-n 6205 which I got using double driver. I am not sure about imaging, I was testing them and did not have time to image just to get them to boot to the KBOX. But it was booting them fine with those two driver in the KBE driver folder
Please log in to comment
I like downloading the nic drivers from the manufacturer's website, as KBE drivers need to be Win7.
Again, I would try our driverpack, download, unzip, but in the kbe_windows_x86 (or x64), reacache and build a new KBE. These driverpacks have been proven to work with everything I've encountered. Don't forget to rebuild KBE, that is the key step.
Corey
Again, I would try our driverpack, download, unzip, but in the kbe_windows_x86 (or x64), reacache and build a new KBE. These driverpacks have been proven to work with everything I've encountered. Don't forget to rebuild KBE, that is the key step.
Corey
Please log in to comment
Comments
Please log in to comment