Wds client ошибка получения ip адреса от сервера dhcp

WdsClient – An error occurred while obtaining an IP address from the DHCP server. Please check to ensure that there is an operation DHCP server on this network segment.

This is the error I got recently when trying to image some new machines for one of the schools I support.

The correct drivers were installed on the WDS server and I’d previously imaged some desktops of the same model with no problems. I tried a new cable and network point, restarted WDS and DHCP on the server all to no avail. All settings on WDS were fine and as they should be.

Do try the above steps first, as 90% of the time it’s resolved by one of them. This problem is also common if you have a faulty or very long network cable.

It turned out that the PC was taking too long to get an IP address, meaning it couldn’t reach the WDS server at the time it tried to. By the time it has been assigned an IP it had already timed out and thrown me this error.

DHCP seemed to be functioning correctly, as other devices were working with no problems – it just seemed to be DHCP and WDS that weren’t working together properly. I needed a way around this, and after a lot of research I found a way to modify my WIM file so it wouldn’t launch the PE until it could ping the server. Obviously if it can ping it has an IP address, so therefore can continue as it should.

Here’s how to do it:

I advise doing this on a client PC, and not the server.

1. Install the Windows AIK. In this example, I am using and deploying Windows 7, so required the Windows 7 AIK.
2. Open “Windows PE Tools Command Prompt” and type the command below that corresponds to the CPU architecture that your current WDS boot image is on:

   • 32bit - copype x86 C:newbootimage

   • 64bit – copype x64 C:newbootimage

     These commands will create a new Windows PE wim image in C:newbootimage. The file path can be altered if you so wish.

3. Go into the WDS console on your server, and export the current image that you’re having trouble booting to. (Right click > Export Image) and copy that to C:oldbootimage on the client PC you created other wim with in the previous step. For the rest of the tutorial, I will assume this file is called wds.wim
4. Mount both images:
   • Mount the image created in step two by running:

      imagex /mountrw “C:newbootimageWinPE.wim” 1 "C:newbootimagemount"

   • Mount the image exported in step three by running:

      imagex /mountrw “C:oldbootimagewds.wim” 2 "C:oldbootimagemount"

5. Now, copy the sources folder from the old boot image (C:oldbootimagemountsources) to the new boot image (C:newbootimagemountsources). This adds the necessary WDS client setup files to the new image.
6. Open the startnet.cmd file (C:newbootimagemountwindowssystem32starnet.cmd) in Notepad.
   The current files will most likely contain very little text. You need to replace the contents with the following:

   @echo off
    wpeinit
    
    @echo Waiting for the WDS server…
    :testagain
    ping –n 1 wds > NUL
    if %errorlevel% == 0 goto pingok
    
    REM wait 3 sec. and try it again
    ping –n 3 127.0.0.1 >nul
    goto testagain
    
    :pingok
    x:sourcessetup.exe /wds /wdsserver:WDS
    

   This small script will keep trying to ping the server called WDS until it receives at reply. At which point it will continue to boot into WDS setup mode.
   You may change the server name from WDS in the script if you wish, however I advise keeping the script as is and adding a DNS entry for the WDS to point to your server’s IP. This way, the wim file is usable across any server / network by just adding a DNS entry.

7. Save changes to the cmd file.
8. Remove all unnecessary components from the new WDS image with the following command:

    peimg /prep mountwindows

9. Unmount the new image and save changes with the following command:

    imagex /unmount /commit mount

10. At this point the new wim image will probably be around 200mb. It’s advised you export the image to a new wim file to reduce it in size with the following command:

     imagex /export “C:newbootimageWinPE.wim” 1 “C:newbootimagenewwds.wim” “Custom WDS Windows PE”

The image at this point is now complete, and will be around 120mb. You can then add this to the boot images section of your WDS server as you normally would with boot.wim from a Windows DVD or ISO.

For your convenience, I have created a Windows 7 32 and 64 bit version of wim which you can download from the following links:

• W732PE.wim
• W764PE.wim

Thanks to svengru at TechNet for sharing his solution. The above is merely a modified version of his solution, clearing up some sections that don’t need to be done post Vista such as importing drivers to the wim.

I have a problem with a Dell 7040 desktop pc. I received the following message.

WDSclient: an error occured while trying to obtain an IP address from the DHCP server. Please check to

ensure that there is an operational DHCP server on this network segment»

Error comes after loading pxe boot. it only comes while loading the install image. on command propmpt i

cant see an ip address.2012.
I created boot and install image of windows 10. injected network drivers of the Dell pc in boot.
Windows 7 image is working fine, problem is with windows 10 image. Even i syprep wim image from the same

dell machine. still same error.

plz advise as im totaly stuck.

Thanks.

check
Best Answer

Hi George,

Today i fixed the issue.

Before i created boot image on wds
from windows 10 DVD containing 1507 build which has issues.

I got an idea to create the boot
image from win 10 build 1607 wich i dowloaded from microsoft.

I created the boot image again with
new build and hurray…!! that creepy error gone and installation was successful.

 Everyone plz create your win10 boot
image from windows 10 latest build. Like 1607 or 1703. I did through 1607.

Much appreciated for your detailed reply.

 best..

1 found this helpful
thumb_up
thumb_down

View Best Answer in replies below

If you are using new (or different) hardware from what you built your Windows image on, you may see:  WdsClient: An Error Occured While Obtaining IP Address From the DHCP Server.  Fortunately, you can ignore most of the other solutions floating around the internet telling you to manually inject the drivers into your image.  Windows Deployment Service (WDS) has a simple mechanism to inject drivers into your image using the WDS GUI.

How to Add Drivers to Windows Deployment Server:

1. Go to your hardware manufacturers website and download the network card driver(s) for the hardware in question
2. Open your WDS MMC, expand the server in question and then expand DRIVERS
3. Select ADD DRIVER PACKAGE,
4. Select SELECT ALL DRIVER PACKAGES FROM A FOLDER and browse to a folder that contains your unpacked drivers
   1. Unpacked drivers means that your driver files must be extracted from their .EXE or .MSI or .ZIP file.
      1. If you do not already know how to do this, download, 7-ZIP and start 7ZIP, select your driver package and click the EXTRACT button
5. In the AVAILABLE DRIVER PACKAGES window just click NEXT
6. In the DRIVER GROUPS window, make sure you choose, SELECT AN EXISTING DRIVER GROUP.
   1. If you do not select a group your drivers will be in WDS but will NOT be applied to any of your images
7. In the TASK COMPLETE window you can click MODIFY THE FILTERS FOR THIS GROUP NOW but I would not
   1. If you add a filter, the drivers will only be applied to devices that meet that filter… I want Windows to figure out if it is needed or not.
      1. The default is “…install all packages that match the installed hardware…” which is good with me

Now you can add those drivers to the image in question.

How to Add Drivers to An Image on your Windows Deployment Server:

1. In WDS, click BOOT IMAGES and right click on the image in question
2. Select ADD DRIVER PACKAGE, then NEXT, then click the SEARCH FOR PACKAGES button
3. The drivers you just added to your WDS server will now appear in the SEARCH RESULTS window
4. Click NEXT, NEXT, NEXT

WDS will then open the image, inject the drivers and close the image.  This is much easier than going through the manual process.

You should not have to restart your WDS service, but if you have troubles, restart it.

Also remember that you will likely want to add these drivers to images other than the BOOT image.  Specifically, you will likely want to repeat the process for the image you are trying to apply and to any CAPTURE image you may have.

I have done the follwoing configurations: Avaiable at: http://technet.microsoft.com/en-us/library/cc770637(WS.10).aspx#BKMK_2

To configure Windows Deployment Services to run on the same computer as Microsoft DHCP

Using the MMC Using WDSUTIL

1.Right-click the server, and then click Properties.

2.On the DHCP tab, select Do not listen on port 67 and Configure DHCP Option 60 to PXEClient (for Windows Server 2008 R2, this option is labeled Configure DHCP option 60 to indicate that this server is also a PXE server).

1.Click Start, right-click Command Prompt, and click Run as administrator.

2.Run WDSUTIL /Set-Server /UseDHCPPorts:No /DHCPOption60:Yes.

To configure Windows Deployment Services to run on the same computer as non-Microsoft DHCP

Using the MMC Using WDSUTIL

1.Right-click the server, and then click Properties.

2.On the DHCP tab, select Do not listen on port 67.

3.Use your DHCP server tools to set the option 60 tag to PXEClient.

1.Click Start, right-click Command Prompt, and click Run as administrator.

2.Run WDSUTIL /Set-Server /UseDHCPPorts:No.

3.Use your DHCP server tools to set the option 60 tag to PXEClient.

To turn on the DHCP authorization requirement

Using the MMC Using WDSUTIL

N/A

1.Click Start, right-click Command Prompt, and click Run as administrator.

2.Run WDSUTIL /Set-Server /RogueDetection:Yes.

To authorize the server in DHCP

Using the MMC Using WDSUTIL

1.Ensure that you are a domain administrator in the root domain of the forest or an enterprise administrator.

2.Right-click the server, and then click Properties.

3.On the Advanced tab, select Authorize the Windows Deployment Server in DHCP.

1.Ensure that you are a domain administrator in the root domain of the forest or an enterprise administrator.

2.Click Start, right-click Command Prompt, and click Run as administrator.

3.Run WDSUTIL /Set-Server /Authorize:Yes.

Client Requests

To configure the server to answer clients

Using the MMC Using WDSUTIL

1.Right-click the server, and then click Properties.

2.On the PXE Response Settings tab, select the appropriate option.

1.Click Start, right-click Command Prompt, and click Run as administrator.

2.Do one of the following:

To respond to all network boot requests, run WDSUTIL /Set-Server /AnswerClients:All.

To respond only to requests from prestaged computers, run WDSUTIL /Set-Server /AnswerClients:Known.

To not answer any requests, run WDSUTIL /Set-Server /AnswerClients:None.

To set a delay in the servers answers to network requests

Using the MMC Using WDSUTIL

1.Right-click the server, and then click Properties.

2.On the PXE Response Settings tab, set the specified time to wait.

1.Click Start, right-click Command Prompt, and click Run as administrator.

2.Run WDSUTIL /Set-Server /ResponseDelay:X, where X is the amount of time (in seconds) you want the server to wait before responding to clients.

_____________________________________________________________________________________Also your post as well states the same:

Quote

Configuring DHCP option 60

The default configuration of Windows Deployment Services assumes that the Microsoft DHCP server and Windows Deployment Services server are on separate physical computers. When DHCP and Windows Deployment Services exist on the same computer, DHCP must inform the client computer that there is a PXE server listening on the network by including DHCP option tag 60 in the DHCP Offer packet.

To configure DHCP option 60 using the Windows Deployment Services snap-in

On the Start menu, click Administrative Tools, and click Windows Deployment Services.

Click to expand the Servers list.

Right-click the server and click Properties.

On the Server Properties page, click the DHCP tab.

On the DHCP Options page, click Configure DHCP Option 60 to ‘PXEClient’.

Additional considerations and references

To perform this procedure, you must be a member of the Account Operators group, Domain Admins group, or you must have been delegated the appropriate authority.

Manage Server Properties

To Configure DHCP option 60 using WDSUTIL

At a command prompt, type: WDSUTIL /set-server /DHCPoption60:yes

Additional considerations and references

WDSUTIL, the Windows Deployment Services command-line management tool, requires elevated privileges to run.

Manage Server Properties

Configuring port 67

Because DHCP listens on port 67 by default, when Windows Deployment Services and DHCP exist on the same computer, the Windows Deployment Services PXE server is not able to listen on port 67 for incoming PXE boot requests.

To configure port 67 using the Windows Deployment Services snap-in

On the Start menu, select Administrative Tools, and click Windows Deployment Services.

Click to expand the Servers list.

Right-click the server and click Properties.

On the Server Properties page, click the DHCP tab.

On the DHCP Options page, click Do not listen on port 67.

Additional considerations and references

To perform this procedure, you must be a member of the Account Operators group, Domain Admins group, or you must have been delegated the appropriate authority.

Manage Server Properties

To configure port 67 using WDSUTIL at a command prompt

At a command prompt, type: WDSUTIL /set-server /usedhcpports:no.

Additional considerations and references

WDSUTIL, the Windows Deployment Services command-line management tool, requires elevated privileges to run.

Manage Server Properties

Important

Both the Configure DHCP Option Tag #60 to PXEClient and Do not listen on port 67 options must be selected if Microsoft DHCP and Windows Deployment Services are running on the same computer»»

…..so i am still in problem i have 2 interfaces of NIC , i try to diable one that i was using for the internet , bit same result, currently i have enabled both interfaces, one is configured with static IP accordingly and on other i am using Internet, this interface DO NOT has static IP.