**Disclaimer: I am a novice in the world of IT. Some of my language won't be accurate. Please bear with me.

I have tried multiple drivers both from HP and Intel but when in a pre boot environment the computer cannot find the NIC driver and as a result will not connect to the K2000 imaging page. I always seem to get stuck on the command prompt that reads as follows:

Administrator: X:\windows\system32\cmd.exe
***Checking if this is a UFD boot and an image is prepped for deployment
***Location KBOX IP address from DHCP option 66 and 244
X:\windows\system32>kgetdhcp 66  1>X:\windows\TEMP\kbox-ip-address
X:\windows\system32>if error level 1 kgetdhcp 244 1>X:\windows\temp\kbox-ip-address
Error: Unable to determine server IP address. Check DHCP options and network drivers.
Warning:Using hardcoded K2000 IP address as fallback
X:\windows\system32>set /p KBOX_IP= 0
***Mounting the KBOX install shares
System error 1231  has occurred
The network location cannot be reached. For information about network troubleshooting, see windows help.
Error: unable to mount KBOX share at \\172.16.16.19\peinst
-----------------------------------------------------------------------------------------------------------------------------------------------------
I know that all this means is that the NIC driver can't be found but I cannot seem to figure out why. I've tried several methods to get around this but I have had no success. Also please note that I can take and image of a HP Z200 with no issues. Does anyone have a solution?

P.S. Here are some specs about the Z440 that may help:
-raid bios
-UEFI

1 Comment   [ + ] Show Comment

Comments

  • This content is currently hidden from public view.
    Reason: Removed by member request
    For more information, visit our FAQ's.
  • When I do an ipconfig the host name is different each time I go through the KBE process. For example the host name most recently returned was minint-1ufa68b and prior to that it was minint-h0omtaa. Do these names mean anything?
Please log in to comment

Answers

0
I do not have any but these steps may fix it for you.
I am assuming w7x64  if not you will just need to get the correct version drivers the rest will be the same.

1.  Connect to your k2 and go to \\ikbox\drivers\kbe_windows_x64.  make a copy of the dirs/files in there on your tech station.  Delete everything out of \\ikbox\drivers\kbe_windows_x64.
2. Go to HP and download and expand the nic drivers.
0mV5mf.jpeg
3. Drop the entire drivers directory on the k2 \\ikbox\drivers\kbe_windows_x64

tiOWC9.jpeg
re-cache the drivers and build a new KBE create a new UEFI boot stick and try that


Answered 12/09/2015 by: SMal.tmcc
Red Belt

  • I tried this method. Sadly, I didn't have any luck. Do you have any other suggestions?
    • check bios version to see if it is most current
      • The current BIOs that I have on this pc is up to date
      • Is there a setting on the PC itself that needs to be configured properly? I can take an image of a Z200 with no issues. The 200 has a normal bot menu but the 400 has a GUI. Also ACHI is currently enable but SATA and IDE are both options for a few different settings. Any other ideas?
Please log in to comment
Answer this question or Comment on this question for clarity

Share