# WDS on IPfire Issues

**URL:** <https://community.ipfire.org/t/wds-on-ipfire-issues/13101>\
**Category:** Network\
**Created:** [28 October 2024 10:08 UTC](https://community.ipfire.org/t/wds-on-ipfire-issues/13101 "2024-10-28T10:08:00Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![bnobnobno](https://community.ipfire.org/user_avatar/community.ipfire.org/bnobnobno/32/11129_2.png) [@bnobnobno](https://community.ipfire.org/u/bnobnobno)\
**Post date:** [28 October 2024 10:08 UTC](https://community.ipfire.org/t/wds-on-ipfire-issues/13101/1 "2024-10-28T10:08:00Z")

</div>

Hello everyone ,

I am using Windows Deployment Services and IPFIRE on our network.  
Recently i made un update on ipfire from 183(or185) to 189.  
After this upgrade WDS is no longer working . I have read all i have seen regarding option 66 and 67 here and tried those settings but i still did not manage to make it boot from WDS.

I will put below some pictures from my case :  
WDS Server = 192.168.0.18  
Client = 192.168.0.222

 ![1](https://community.ipfire.org/uploads/default/original/2X/1/1a70beb2b5df5b0551b57c1d27eb7a0f8dcb03c5.png)  
 ![2](https://community.ipfire.org/uploads/default/original/2X/5/5a02aa27b7e729664c30d24c3d0fdc68f48514fe.jpeg)

If anyone has any ideea what to try next please adivse.  
Thank you .

---

<div class="post-metadata">

**Author:** ![hvacguy](https://community.ipfire.org/user_avatar/community.ipfire.org/hvacguy/32/8576_2.png) [@hvacguy](https://community.ipfire.org/u/hvacguy)\
**Post date:** [28 October 2024 10:28 UTC](https://community.ipfire.org/t/wds-on-ipfire-issues/13101/2 "2024-10-28T10:28:58Z")

</div>

I have a PXE server on my netwok.  
Have not used it in awhile.  
Here is where I set it up

 ![image](https://community.ipfire.org/uploads/default/original/2X/8/8e1902e867114984d42b4165301122b41006bf61.png)

---

<div class="post-metadata">

**Author:** ![bnobnobno](https://community.ipfire.org/user_avatar/community.ipfire.org/bnobnobno/32/11129_2.png) [@bnobnobno](https://community.ipfire.org/u/bnobnobno)\
**Post date:** [28 October 2024 10:44 UTC](https://community.ipfire.org/t/wds-on-ipfire-issues/13101/3 "2024-10-28T10:44:27Z")

</div>

Thanks Shaun , i have tried this , i get on client : There was a TFTP error.

---

<div class="post-metadata">

**Author:** ![arne\_f](https://community.ipfire.org/user_avatar/community.ipfire.org/arne_f/32/12760_2.png) [@arne\_f](https://community.ipfire.org/u/arne_f)\
**Post date:** [28 October 2024 12:36 UTC](https://community.ipfire.org/t/wds-on-ipfire-issues/13101/4 "2024-10-28T12:36:39Z")

</div>

> [@bnobnobno](#):
>
> . I have read all i have seen regarding option 66 and 67 here and tried those settings but i still did not manage to make it boot from WDS.

Have you set “next server” to your wds server ip and the “filename” to “\boot\x86\wdsnbp.com” ?

---

<div class="post-metadata">

**Author:** ![bnobnobno](https://community.ipfire.org/user_avatar/community.ipfire.org/bnobnobno/32/11129_2.png) [@bnobnobno](https://community.ipfire.org/u/bnobnobno)\
**Post date:** [28 October 2024 12:50 UTC](https://community.ipfire.org/t/wds-on-ipfire-issues/13101/5 "2024-10-28T12:50:12Z")

</div>

I have set the IP of the WDS server in next server box but if i set the filename i get this DHCP Failed instead of There was a server timeout.  
I tried with : \boot\x86\wdsnbp.com , boot\x86\wdsnbp.com , and xtih x64 instead of x86. Also tried with what Shaun sugested as a filename.  
PS before the update when this worked i did not had anything there , both boxes (next server and filename) were empty and it worked.

 ![3](https://community.ipfire.org/uploads/default/original/2X/1/18219e226e8cca2e683df085a672d74ec2d17225.jpeg)

Could it be related to this in the last update?  
 ![image](https://community.ipfire.org/uploads/default/original/2X/c/c2fc6fc488f9703ac0cfdca7d34a71481dadefa5.png)

---

<div class="post-metadata">

**Author:** ![arne\_f](https://community.ipfire.org/user_avatar/community.ipfire.org/arne_f/32/12760_2.png) [@arne\_f](https://community.ipfire.org/u/arne_f)\
**Post date:** [28 October 2024 14:37 UTC](https://community.ipfire.org/t/wds-on-ipfire-issues/13101/6 "2024-10-28T14:37:34Z")

</div>

> [@bnobnobno](#):
>
> Could it be related to this in the last update?

No. This has nothing to do with the dhcp server. dhcpcd is the dhcp client that IPFire use for red connection.

---

<div class="post-metadata">

**Author:** ![hvacguy](https://community.ipfire.org/user_avatar/community.ipfire.org/hvacguy/32/8576_2.png) [@hvacguy](https://community.ipfire.org/u/hvacguy)\
**Post date:** [28 October 2024 14:45 UTC](https://community.ipfire.org/t/wds-on-ipfire-issues/13101/7 "2024-10-28T14:45:31Z")

</div>

Per your Picture

See file name above.  
Looks like it is finding your server  
At 192.168.0.18 that is good.  
The file is listed above too.  
Fault may be at server  
Would look there.

---

<div class="post-metadata">

**Author:** ![bnobnobno](https://community.ipfire.org/user_avatar/community.ipfire.org/bnobnobno/32/11129_2.png) [@bnobnobno](https://community.ipfire.org/u/bnobnobno)\
**Post date:** [28 October 2024 15:11 UTC](https://community.ipfire.org/t/wds-on-ipfire-issues/13101/8 "2024-10-28T15:11:27Z")

</div>

Thanks Shaun , I checked everything on WDS , all settings , firewall is off , also what is strange that no changes were made on the WDS server for a long time. Only i have access to it . Thanks.

---

<div class="post-metadata">

**Author:** ![bnobnobno](https://community.ipfire.org/user_avatar/community.ipfire.org/bnobnobno/32/11129_2.png) [@bnobnobno](https://community.ipfire.org/u/bnobnobno)\
**Post date:** [29 October 2024 08:59 UTC](https://community.ipfire.org/t/wds-on-ipfire-issues/13101/9 "2024-10-29T08:59:23Z")

</div>

I reinstall on a different physical server the WDS role and it works now.It was something related just to that server.  
PS : regarding IPFIRE i did not had to do anything or set anything it worked just good without changeing or addining anything at nex-server or filename. Thanks guys for helping. Have a good day.
