This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(252.8, 57.99999999999999%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESC%3C/text%3E%3C/svg%3E)
wds client: an error occurred while obtaining an ip address from the dhcp server. please check to ensure that there is an operational dhcp server on this network segment.
What is the main cause of this error?
How do I fix the issue without going to the wds server system?
@Sunirmal Chakraborty
Hi,
This error is almost a missing driver in the boot.wim.
You could follow the following methods to inject drivers into your image using the WDS GUI.
https://www.urtech.ca/2018/10/solved-wdsclient-an-error-occured-while-obtaining-ip-address/
Note: This is a third-party link and we do not have any guarantees on this website. And Microsoft does not make any guarantees about the content.
Also, creating your win10 boot image from windows 10 latest build may work.
Hope above information can help you.
============================================
If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(41.6, 95%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECR%3C/text%3E%3C/svg%3E)
Thanks for the tip ! What strike me though is that the NIC works well connecting to the WDS and get the boot.wim but fail to get an IP later on... I guess it has to do with the PXE environment vs the Windows PE ?