Post Reply 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
2017-10-16, 16:38
Post: #2
Start with testing the latest version of ipxe, simplest case is to ctrl-b then type dhcp followed by chain

You should just let it autoboot from the normal WDS server (make sure you don't have any specific iPXE configuration in place)

The message you get must be from the windows parts itself.
Since logging of the WDS TFTP server don't give much useful information I would resort to using packet capture, such as with wireshark on the server to grab what is actually happening, both DHCP and TFTP packets are of interest (make sure to also include proxydhcp packets). And then maybe compare that to a case where it does work.

iPXE uses reconstructed DHCP packets which might be the reason that WDS don't get the information it needs.

This information might not get you all the way to the goal, but at least it should get you part of the way.

Use GitHub Discussions
VRAM bin
Visit this user's website Find all posts by this user
Quote this message in a reply
Post Reply 

Messages In This Thread
IPXE and WDS - Mangosniper - 2017-10-16, 14:20
RE: IPXE and WDS - NiKiZe - 2017-10-16 16:38
RE: IPXE and WDS - Mangosniper - 2017-10-23, 07:26

User(s) browsing this thread: 1 Guest(s)