Have you applied SU3? Is the client config set to enable PXE Self-Electing that is deployed to at least one available computer in that subnet?
There's a bit of additional logic involved as well (and yes - the upgrade to SU3 may be a good idea).
For instance - is your device a laptop / does it have A wIfI NIC? If so, we'll generally NOT let it elet itself as a PXE-rep as "laptops that wander off" make for undesirable PXE reps and (worse) "PXE over WiFi NIC" tends to work barely if ever at all. So there's more to the decision process involved.
For much the same reason we shouldn't let a touch-pad be elected to be a PXE rep.
If you still have the problem with the latest patch set, providing more information on the device and getting in touch with support who can have a look at it, may help clarify why that device isn't doing it. The intention is that this should be as "low touch" for you as possible in the end ... but to understand the decision, we'd need to look at the device / configuration in detail, potentially .
Hope that helps / makes sense.
Ha, now I have the same issue on a PXE Rep after updating to 2017.3. Did you ever find a solution to this?
Whatever was causing it for me worked itself out on that machine. I tried a bunch of things, none of which worked, but then it randomly started working a few hours later...
Meh - everyone's favourite issues ... "the disappearing trick" ... ah well - keep an eye open or so. Maybe we can figure out what the commonalities are.