Troubleshooting Driver Issues in KBE (Example error 1231) (4300212)

ERROR: Unable to determine server IP address. Check DHCP options and network drivers. WARNING: Using hardcoded SDA 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 \\xxx.xxx.xxx.xxx\peinst

EXAMPLE:

Another possible error is:  return code:3221225477 when applying an image.

Network or Storage Driver fails to Load during boot to a new model.  The network driver for the specific system is missing from the existing KBE boot environment.  If there is an existing driver pack, it may need to be replaced by a newer driver pack.  If the latest driver pack does not have the correct network driver for the specific system then it will have to be downloaded and included into the \driver share.

Example errors:

NIC: Unable to PXE boot into KACE / Unable to determine server IP address / System error 1231 has occurred

Storage: Return code:3221225477  / System error 1231 has occurred

Verify latest driver pack:

Make sure that the latest WINPE10 driver pack is used as that driver pack is periodically updated for Windows 10 (but still includes some of the newer Windows 7 drivers).

Network Driver:

Type ipconfig, if no ip address is shown, the WinPE Environment or KBE lacks the appropriate driver.

Note: Windows 7 for WinPE 3, Windows 8 for WinPE 4, Windows 8.1 for WinPE 5, Windows 7, 8.x, 10 for WinPE 10.

1. Obtain the correct driver from the vendor's site.
2. Place it onto a usb key, plug the key into the machine [the usb key will automount and one can type diskpart >  list vol, to determine the correct drive letter].
3. Type drvload e:\whatever.inf [assuming e: is the drive letter of the usb key and whatever.inf is the applicable driver information file and it's on the root of the usb key.
4. Type ipconfig to obtain an ip via dhcp
5. Type startnet.cmd and it should load into the KBE main menu, assuming the driver loaded successfully.

You will then know it's the correct driver, which you can add to \ikbox\kbe_windows_xXX to rebuild the KBE for a permanent fix [after removing any duplicate drivers from the share, first].

For example, if this is a Latitude 5480, the latest network driver is identified as Intel I2xx/825xx Gigabit Ethernet Network Controller Driver (at the time of this writing).  Download the driver and then extract it, you can use a 3rd party tool to extract the compressed file and drill into the following folders: \Network_Driver_WJ8PK_WN32_21.1.30.0_A00_01\production.  It should display the following OS architecture subfolders available:

The example laptop, Latitude 5480 at the time of this writing, is able to load a network driver called E1R65x64.inf:

Storage:

Note: Windows 7 for WinPE 3, Windows 8 for WinPE 4, Windows 8.1 for WinPE 5, Windows 7, 8.x, 10 for WinPE 10.

1. Obtain the correct driver from the vendor's site.
2. Place it onto a usb key, plug the key into the machine [the usb key will automount and one can type diskpart >  list vol, to determine the correct drive letter].
3. Type drvload e:\example.inf [assuming e: is the drive letter and example.inf is the applicable driver information file and its on the root of the USB key.
4. Type diskpart
5. Type rescan, then list disk and finally exit.

You will then know it's the correct driver [assuming the disk was listed via diskpart], which you can add to \ikbox\kbe_windows_xXX to rebuild the KBE for a permanent fix [after removing any duplicate drivers from the share, first].

Note: For steps needed to rebuild KBE please see How to create a KBE pre-boot environment.