Wdsclient ошибка при получении ip - Не ошибается лишь тот, кто ничего не делает!

При загрузке образа с WDS появляется ошибка

WdsClient: ошибка получения IP-адреса от сервера DHCP.

Не могу понять, что делать.
я пробовал подкидывать драйвера вручную по инструкции.

https://support.microsoft.com/ru-ru/kb/923834

Пробовал через сам WDS к boot образу докидывать драйвера, но все равно ничего.
Может я что-то не то делаю? Кто-нибудь сталкивался с такой бедой?
Сам wds настроен нормально, потому что такая проблема не на всех компах. Wds+DHCP и порт настроен нормально.
Спасибо

Вопрос задан

более трёх лет назад
2801 просмотр

Пригласить эксперта

WdsClient: ошибка получения IP-адреса от сервера DHCP.

Где вы такое ловите?
Вообще, встречал такие сетевки встроенные, на которых PXE отказывался работать вообще. Ссылаюсь на кривизну чипа сетевой карты.

Проблема скорее всего с драйверами. Если сделать shift+F10, ipconfig /all, то видно что сетевухи нет. Значит драйвера на нее не установились в загрузочном образе.
С аналогичной проблемой сталкиваюсь не первый раз. Обычно легко интегрируются драйвера. Сейчас на intel i219 не получается. Новые матери h410 не поддерживаются из коробки последним релизом W10 (2004).

Возьмите образ boot.wim из Windows Server 2022, на нём всё работает.

WDS стоит на Windows server 2019, разворачиваю Windows 10
Проблема актуальная до сих пор, причем проблема на сетевых картах intel i219 и выше. Дистрибутив свежий, версия сборки 10.0.19041 . Драйвера в образе на сетевые карты есть

Показать ещё
Загружается…

04 июн. 2023, в 16:00

200 руб./за проект

04 июн. 2023, в 15:02

2000 руб./за проект

04 июн. 2023, в 14:16

1500 руб./за проект

Минуточку внимания

Источник

Remove From My Forums

Вопрос
Доброго времени суток.

Есть проблема связаная с работой WDS на Windows Server 2008 R2. PXE клиент стартует олично происходит получение IP адреса от DHCP сервера, выбираю образ загрузки после чего получаю сообщение
«WDSClient: ошибка при получении IP-адреса от сервера DHCP. Проверьте наличие рабочего DHCP-сервера в данном сегменте сети».

До этого сервер писал что он не может найти сетевой драйвер и просил включить его в образ загрузки, что я собственно говоря и сделал. Но теперь вот эта ошибка!Товарищи IT специалисты помогите в решении этой проблемы, потому что вариантов
для её решения у меня нет.

Спасибо заранее за помощь

Ответы

Не работает на конкретном оборудовании или во всей сети? Судя по всему на конкретном, раз драйвер искали. Очень вероятно, что драйвер кривой. Если образ загрузки у Вас взят от 7 32, то и драйвер сетевой нужен для 7 32. Аналогично для всех остальных систем.
WDS и DHCP у Вас работают корректно и выдают именно то, что и должны. Сначала DHCP адрес получает адаптер, а потом образ PE подгружает драйвер и получает адрес уже сам. Вот в драйвере и проблема.

Все, указанное выше, является моим личным мнением. Если Вам помогли предложенные рекомендации, пожалуйста, помечайте их, как ответ. Это поможет другим пользователям быстрее найти решение.
- Помечено в качестве ответа
  
  22 августа 2011 г. 8:22

Источник

Перейти к контенту

Remove From My Forums

Question
Trying to create and deploy a Windows 7 pro image for Dell optiplex 390s. Getting the dreaded error above when trying to connect to the DHCP. After a couple days of research I’ve tried injecting drivers, different version of drivers, injecting drivers into
a different boot image, changing the name and/or deleting the setup.exe file from the image, verified that spanning-tree portfast was enabled on the switch, and edited windowssystem32startnet.cmd. Everything i’ve tried results in the error still showing.

When running ipconfig it looks like the NIC is not even initializing which leads me to believe it’s a driver issue still. I’m out of ideas on this one. Anyone else have any?

Answers

Yes, I agree that this seems to be a driver issue.

Please follow the steps below to find the correct NIC driver for the problematic clients and create a new boot image, then add the NIC drivers to the new boot image for a test.

Error message when you start a PXE client to connect to a WDS server on a Windows Server 2003 SP1-based computer or on a Windows Server 2008-based computer: «WdsClient: An error occurred while starting networking»

http://support.microsoft.com/kb/923834

Thanks
Zero

Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
- Proposed as answer by
  
  Tuesday, October 9, 2012 1:26 AM
- Marked as answer by
  LudoTheGreat
  Tuesday, October 9, 2012 1:27 AM

Remove From My Forums

Question
My WDS has been working for a month now. A few days ago, My WDS service just stop working. I tried everything to get back up an running. Nothing worked. I removed the role and re-add it. It worked for a few more days and then the service just stop working
again. Tried everything again to try to fix it, But nothing worked. Removed the role again and re-add it. Now when I boot up into PXE and select my Boot option, I am getting an error «WDSclient an Error occurred while obtaining an ip address from the
dhcp». Plug my laptop into the port and was able to get an IP address. Some of the forums say it’s a driver issue. The driver where working just fine before. I did make a new driver package to see if that would work. Nothing. I did try this http://www.broexperts.com/2014/12/solution-dhcp-error-in-wds-server-2008-r2/,
Didn’t work.

I am on Server 2012 R2 and SCCM is on the same server (I don’t know if that has anything to do with it. The PXE has been disabled on it)
- Edited by
  
  Thursday, April 9, 2015 2:32 PM

Answers

Hi matkat1,

Some folk meet your similar case when then use NIC driver from DELL, you can try to update the BISO then monitor this issue again, if it not work please removed the Switch and
monitor whether it able to deploy the image.

ON the DHCP server, please check to ensure that there is an operational DHCP server network segment and if your DHCP server on your WDS server please reauthorized with the DHCP.

Please also check whether the event 4101 occurred and indicate the TFTP download failed.

More information:

WDS Client DHCP issues… Here is one solution

http://blogs.technet.com/b/svengruenitz/archive/2008/06/30/wds-client-dhcp-issues-here-is-one-solution.aspx

WdsClient: An error occurred while obtaining an IP address from the DHCP server

https://social.technet.microsoft.com/Forums/windows/zh-CN/a5bb3e6d-7602-40e0-b45b-b89578ef64f1/wdsclient-an-error-occurred-while-obtaining-an-ip-address-from-the-dhcp-server?forum=w7itproinstall

I’m glad to be of help to you!

Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com
- Proposed as answer by
  Alex Lv
  Wednesday, April 22, 2015 7:55 AM
- Marked as answer by
  Alex Lv
  Wednesday, April 29, 2015 2:58 AM

Remove From My Forums

Question
My WDS has been working for a month now. A few days ago, My WDS service just stop working. I tried everything to get back up an running. Nothing worked. I removed the role and re-add it. It worked for a few more days and then the service just stop working
again. Tried everything again to try to fix it, But nothing worked. Removed the role again and re-add it. Now when I boot up into PXE and select my Boot option, I am getting an error «WDSclient an Error occurred while obtaining an ip address from the
dhcp». Plug my laptop into the port and was able to get an IP address. Some of the forums say it’s a driver issue. The driver where working just fine before. I did make a new driver package to see if that would work. Nothing. I did try this http://www.broexperts.com/2014/12/solution-dhcp-error-in-wds-server-2008-r2/,
Didn’t work.

I am on Server 2012 R2 and SCCM is on the same server (I don’t know if that has anything to do with it. The PXE has been disabled on it)
- Edited by
  
  Thursday, April 9, 2015 2:32 PM

Answers

Hi matkat1,

Some folk meet your similar case when then use NIC driver from DELL, you can try to update the BISO then monitor this issue again, if it not work please removed the Switch and
monitor whether it able to deploy the image.

ON the DHCP server, please check to ensure that there is an operational DHCP server network segment and if your DHCP server on your WDS server please reauthorized with the DHCP.

Please also check whether the event 4101 occurred and indicate the TFTP download failed.

More information:

WDS Client DHCP issues… Here is one solution

http://blogs.technet.com/b/svengruenitz/archive/2008/06/30/wds-client-dhcp-issues-here-is-one-solution.aspx

WdsClient: An error occurred while obtaining an IP address from the DHCP server

https://social.technet.microsoft.com/Forums/windows/zh-CN/a5bb3e6d-7602-40e0-b45b-b89578ef64f1/wdsclient-an-error-occurred-while-obtaining-an-ip-address-from-the-dhcp-server?forum=w7itproinstall

I’m glad to be of help to you!

Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com
- Proposed as answer by
  Alex Lv
  Wednesday, April 22, 2015 7:55 AM
- Marked as answer by
  Alex Lv
  Wednesday, April 29, 2015 2:58 AM

При загрузке образа с WDS появляется ошибка

WdsClient: ошибка получения IP-адреса от сервера DHCP.

Не могу понять, что делать.
я пробовал подкидывать драйвера вручную по инструкции.

https://support.microsoft.com/ru-ru/kb/923834

Вопрос задан

более трёх лет назад
2549 просмотров

Пригласить эксперта

WdsClient: ошибка получения IP-адреса от сервера DHCP.

Возьмите образ boot.wim из Windows Server 2022, на нём всё работает.

Показать ещё
Загружается…

10 февр. 2023, в 08:22

2000 руб./за проект

10 февр. 2023, в 04:49

50000 руб./за проект

10 февр. 2023, в 02:20

3000 руб./за проект

Минуточку внимания

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

Read these next…

Can’t communicate with scanner

Hardware

Hello everyone,I have a client that uses Kodak ScanMate i940 scanners at their desks. They recently got a new computer that we prepped and put on their domain. This new computer is recognizing the scanner but it is unusable with the error «can’t communica…
Different MAC address, same computer name — multiple DHCP leases

Windows

I’m noticing a lot more now that our Wifi DHCP scopes are filled by the same computer name, but with different mac addresses. I know there’s a feature in Windows 10 called Random hardware addresses, but that setting is off. Is there anything else that cou…
Snap! — No-Password Logins, Solar Powered Water Filter, Glitch in the Matrix?

Spiceworks Originals

Your daily dose of tech news, in brief.

Welcome to the Snap!

Flashback: February 9, 1996: Introduction of the Bandai Pippin (Read more HERE.)

Bonus Flashback: February 9, 1990: Galileo Probe does a Venus Flyby (Read more HERE.)

You nee…
Roku TV being used as Wallboard Issues

Hardware

Helping someone out at their shop. They have 4 large Roku screens and 2 laptops with dual HDMI ports for video. They are viewing static website business dashboards and PowerPoint. At first all 4 screens connected to wireless, worked for a while but with a…
Charging for SSO

Security

We have SSO set up with around 5 or 6 solution providers via our M365. Not one of them charges for this, they just sent us the documentation.I identified another online service in use by one of our departments which would benefit from using SSO for staff …

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.

Install the Windows AIK. In this example, I am using and deploying Windows 7, so required the Windows 7 AIK.
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.
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

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"

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.
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.
Save changes to the cmd file.
Remove all unnecessary components from the new WDS image with the following command:
```
 peimg /prep mountwindows
```
Unmount the new image and save changes with the following command:
```
 imagex /unmount /commit mount
```
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.

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:

Go to your hardware manufacturers website and download the network card driver(s) for the hardware in question
Open your WDS MMC, expand the server in question and then expand DRIVERS
Select ADD DRIVER PACKAGE,
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
In the AVAILABLE DRIVER PACKAGES window just click NEXT
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
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:

In WDS, click BOOT IMAGES and right click on the image in question
Select ADD DRIVER PACKAGE, then NEXT, then click the SEARCH FOR PACKAGES button
The drivers you just added to your WDS server will now appear in the SEARCH RESULTS window
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.

Источник

Remove From My Forums

Question
Hi!

I’m trying to deploy a WDS server for a while, but I get the next error (but then in dutch):
WdsClient: An error occurred while obtaining an IP address from the DHCP server. Please check to ensure there is an operational DHCP Server on this network segment.The
server I work with is Server 2012R2.

What I have tried:
- Downloaded and implemented all 16 ethernet drivers for the client (HP Probook 430 G2) by the WDS «add drivers» feature.
- Implemented all drivers from an official W7 «Applications and Driver Recovery DVD» in WDS. (this solved an missing driver error earlier)
- tried a different boot.wim and install.wim from another Windows 7 pro .iso.
- Tried 4 different HP computers (3 laptops and 1 desktop). one of these laptops is my own computer, which worked fine by another WDS server from my last traineeship.
- Installed the server on a different computer.
- Reinstalled the Server like 4 times totally.
- Rebuilded everything in VMware Workstation, everything works fine in here untill I connect a physical computer by peer-to-peer cable, than I get the error again (drivers from HP site and CD as told above are added).
- The different networks I tried: a cisco switch with 4 clients and 1 server attached, nothing more. I read about the portforwarding problem in cisco switches, so I tried peer-to-peer between a physical Server and client and like I said between a virtual
  switch in vmware.
- First installed the server with the DHCP role, tested the connections, IP addresses are leased and I can ping while clients are in Windows 7.
- I get the error while running the setup from the boot.wim, so I have a connection with the server, however if I start a command prompt by SHIFT+F10 and put «ipconfig» in, the results are pretty empty: «Windows IP-configuration«.
  Even after a few minutes I have no IP configuration. Results of the command «ipconfig /renew» is: «An error occured while releasing interface Loopback Pseudo-Interface 1: The system cannot find the file specified.«
- DHCP configuration on active scope: 60 «PXEClient» and 66 for the ip address of my WDS server.
- DHCP properties in WDS: «Do not listen on DHCP ports» and «Configure DHCp options to indicate that this is also a PXE server» are enabled because my Windows DHCP role is active beside the WDS role on the same phisical server.
- Configured the windowssystem32startnet.cmd succesfully in a mounted image 3 times from different suggestions, doesn’t help me either.
I read aslwell that it could be something with HP. I only have 1 DHCP server active to be clear. I’m not using DNS. My teachers at school can’t help me, I hope someone here can! I would be amazing happy if the problem wille be solved.

Thanks!

Answers

Hi Alex,

>> I get the error while running the setup from the boot.wim, so I have a connection with the server, however if I start a command prompt by SHIFT+F10 and put «ipconfig» in,
the results are pretty empty: «Windows IP-configuration». Even after a few minutes I have no IP configuration. Results of the command «ipconfig /renew» is: «An error occured while releasing interface Loopback Pseudo-Interface 1: The
system cannot find the file specified.»

According your description,it seems to be a driver issue. As far as I know,you should extract and only add the corresponding Drivers into the boot image,if you added them all, you will
getting hardware errors on the PC.

Best Regards,

Cartman

Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you
have feedback for TechNet Support, contact tnmff@microsoft.com.
- Marked as answer by
  
  Thursday, March 10, 2016 9:33 AM

Источник

Я использую Windows 2012 server R2’s WDS для установки образов win10 на клиентские ПК, которые представляют собой комбинации HP ProBook 450, 430 и HP ProDesk 400 G1. Недавно я купил несколько HP ProDesk 600 G2, и теперь мой отлично работающий образ WDS не любит новый рабочий стол HP.

Я подключил новый ПК через LAN-кабель к сети и выполнил загрузку по сети, после чего выбрал нужный загрузочный образ. Затем выбрал установочный образ и получил экран «Установка начинается». После нескольких минут размышлений я получил
"WdsClient: произошла ошибка при получении IP-адреса от DHCP-сервера. Пожалуйста, убедитесь, что в этом сегменте сети есть рабочий DHCP-сервер.«

Я проверил данные аренды DHCP, и клиентский ПК смог получить IP-адрес через DHCP-сервер.

Кстати, DHCP и WDS находятся в одной подсети.

Проведя небольшое исследование, я обнаружил, что это проблема с драйвером ethernet. Поэтому сейчас я пытаюсь добавить пакет сетевого драйвера в загрузочный образ, надеясь, что смогу загрузить сетевой драйвер во время PE, если проблема в драйвере.

Я могу выбрать пакет сетевого драйвера следующим образом

AddDriverPackage

Затем он выдает «Dism host servicing process has stopped working»

После закрытия диалогового окна выдает следующую ошибку «Operation failed" с "class not registered`»

OperationFailed

Однако, как гласит ошибка, я подумал, что проблема в «Netwew01[x64]» «имени файла Netwew01.INF» и в следующий раз, когда я запустил его, я не выбрал «networkw01.INF«. После этого снова появилась та же ошибка отсутствия реакции и та же ошибка «class not registered«, но указывающая на другой набор драйверов («ansmw60e.INF«). Однако я попробовал снова удалить второй набор драйверов, и то же самое произошло с другим набором драйверов.

Не мог бы кто-нибудь помочь мне с этой проблемой: либо исправить начальную проблему, либо вторую часть?

Источник

Минуточку внимания

Вопрос

Ответы

Question

Answers

Question

Answers

Question

Answers

Минуточку внимания

Read these next…

Can’t communicate with scanner

Different MAC address, same computer name — multiple DHCP leases

Snap! — No-Password Logins, Solar Powered Water Filter, Glitch in the Matrix?

Roku TV being used as Wallboard Issues

Charging for SSO

How to Add Drivers to Windows Deployment Server:

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

Question

Answers