Microsoft KB Archive/923834

= Error message when you start a PXE client to connect to a WDS server on a Windows Server 2003 SP1-based computer: &quot;WdsClient: An error occurred while starting networking&quot; =

Article ID: 923834

Article Last Modified on 7/25/2007

-

APPLIES TO

 Microsoft Windows Server 2003 Service Pack 1, when used with:  Microsoft Windows Server 2003, Standard Edition (32-bit x86)

 Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)

 Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)

 Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems</li></ul>

 Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems</li></ul> </li></ul>

-

<div class="symptoms_section">

SYMPTOMS
Consider the following scenario. You start a Pre-boot execution Environment (PXE) client to connect to a Microsoft Windows Server 2003 Service Pack 1 (SP1)-based computer. This computer is running Windows Deployment Service (WDS). In this scenario, you receive an error message that resembles the following:

WdsClient: An error occurred while starting networking: a matching network card driver was not found in this image. Please have your Administrator add the network driver for this machine to the Windows PE image on the Windows Deployment Services server.

<div class="cause_section">

CAUSE
This issue occurs if the WDS boot image does not contain a network driver for your third-party network adapter.

<div class="resolution_section">

RESOLUTION
To resolve this issue, follow these steps: <ol> Find the network driver that is missing from the WDS boot image. To do this, follow these steps: <ol style="list-style-type: lower-alpha;"> When you receive the error message that is mentioned in the &quot;Symptoms&quot; section, press SHIFT+F10 to open a command prompt.</li> At the command prompt, type the following command:

Notepad.exe x:\Windows\INF\setupapi.app.log

</li>  In the Setupapi.app.log file that is displayed, locate the section that identifies the Plug and Play ID (PnPID) of the third-party network adapter. For example, &quot;DIF_SELECTBESTCOMPATDRV - PCI\VEN_10B7&DEV_9200&SUBSYS_010D1028&quot; is the section that identifies the PnPID of the network adapter in the following Setupapi.app.log file: >>> [DIF_SELECTBESTCOMPATDRV - PCI\VEN_10B7&DEV_9200&SUBSYS_010D1028&REV_78\4&19FD8D60&0&60F0] >>> Section start 2006/05/05 12:42:59.281 cmd: X:\Sources\setup.exe dvi: No class installer for 'Ethernet Controller' dvi: No CoInstallers found dvi: Default installer: Enter dvi:     {Select Best Driver} !   dvi:           Selecting driver failed(0xe0000228) dvi:     {Select Best Driver - exit(0xe0000228)} !   dvi: Default installer: failed! !   dvi: Error 0xe0000228: There are no compatible drivers for this device. <<< Section end 2006/05/05 12:42:59.296 <<< [Exit status: FAILURE(0xe0000228)] </li> Locate the correct driver for the network adapter that you identified in step 1c. Then, copy the driver onto a floppy disk or onto a universal serial bus (USB) flash drive.</li></ol> </li> Manually load the network driver, and then verify that it is the correct driver. To do this, follow these steps: <ol style="list-style-type: lower-alpha;"> At a command prompt, type the following command, and then press ENTER:

drvload .inf

Notes   .inf is the name of the third-party network driver.</li> You have to specify the full path and the name of the driver. For example, if .inf is on a CD, and the CD drive is drive D, type the following command, and then press ENTER:

drvload.exe d:\ \ .inf

</li></ul> </li> Type wpeutil InitializeNetwork, and then press ENTER.</li> To verify network connectivity, type ipconfig /all.

Note The ipconfig /all command generates a detailed configuration report for all interfaces that include any remote access adapters.</li></ol> </li> Update the WDS boot image to include the new third-party network driver. To do this, follow these steps.

Note The following procedure assumes that the Windows Automated Installation Kit (AIK) is installed on the WDS server. If the Windows AIK is not installed on the WDS server, you can perform the same procedure on another computer that does have the Windows AIK installed. Then, map a network drive to the WDS server. <ol style="list-style-type: lower-alpha;"> On the WDS server, click Start, click Run, type wdsmgmt.msc, and then press OK.</li> <li>Under your WDS server, double-click Boot images.</li> <li>Right-click the boot image that you want, and then click Disable.</li> <li>Right-click the same boot image, click Properties, and then click General.</li> <li>Note the name and location of the boot image that is displayed in the File name box.</li> <li>At a command prompt, type the following:

C:\program files\windows aik\tools\petools\copype.cmd x86 c:\windowspe-x86

Note Keep this command prompt window open for the next step.

Imagex /info \remoteinstall\boot\x86\images\ .wim

Notes <ul> <li> :\remoteinstall represents the path at which the Remoteinstall folder is installed.</li> <li> .wim is the name of the boot image.</li></ul> </li> <li>Note the boot index number of the bootable image that is displayed. To identify the boot index number, locate the line that contains &quot;boot index: .&quot;

Note  is the boot index number. The number indicates that image number  is marked as bootable and that the image is to be updated. The second image is the default image that you would typically modify. However, always verify which image is marked as bootable.</li> <li>At a command prompt, type the following:

Imagex /mountrw :\remoteinstall\boot\x86\images\boot.wim 2 mount

peimg /inf=driver.inf mount\Windows

imagex /unmount /commit mount

Notes <ul> <li> :\remoteinstall represents the path at which the Remoteinstall folder is installed.</li> <li> .inf is the name of the third-party driver.</li> <li>The Imagex /mountrw command mounts the specified image, with read/write permissions, to the specified directory.</li></ul> </li></ol> </li> <li>Enable the boot image on the WDS server. To do this, follow these steps: <ol style="list-style-type: lower-alpha;"> <li>On the WDS server, click Start, click Run, type wdsmgmt.msc, and then click OK.</li> <li>Under  , double-click Boot images.</li> <li>Right-click the boot image that you want, and then click Enable.</li></ol> </li></ol>

Notes <ul> <li>Any errors that are generated when you follow these steps have standard Win32 error codes. For more information about Win32 error codes, search the Microsoft Knowledge Base. To do this, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=FH;EN-US;KBHOWTO

</li> <li>Back up the boot image before you mount it in step 3h.</li></ul>

Keywords: kbtshoot kberrmsg kbprb KB923834

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.