@george1421
Here is the latest copy (I rebuilt the box to a different environment but had the same issue this is the latest copy, hence I think I’ve done something dumb).

@george1421

So what’s up with the sym link? Its working perfectly now.

@george1421 I can grab the undionly.kxpe but not the undionly.0. ‘I get connect request failed’

@george1421 hmm… So why won’t it grab the file on PXE boot? I’m afraid I’m not strong in this area but I get the feeling that there something really silly that I’ve missed.

@george1421 Here is the contents of the tftpboot directory (just resnapped it):

Does this look right?

@george1421 Hi! Sorry, my boss send me on a three week escapade with a days notice, I’m back now. Eureka! I think we may have found the problem. I can tftp many files but not the undionly.0 file. See below:

How do I fix that? Could it be permissions on the other side of the sym link?

@george1421 hmmm, ok. I’ll try it on a physical machine and see if its not just an issue with the vm’s that I’m using. It will take me a day or so to get a lab up and running. Let you know ASAP.

Thank you once again for your support, incredible how well you look after the community :).

@george1421 Thank you again. No luck with the pxe-service line:

See attached the pcap file:

0_1490611720374_output.pcap

I needed to modify the tcpdump command a smidge to make it work:

tcpdump -w /output.pcap port 67 or port 68 or port 69 or port 4011 -i ens33

@george1421 I tried that, same error. Here is the tftboot folder with sym links:

Is that right?

@george1421 I believe its a legacy device. Its a windows 7 VM, not sure if that would use UEFI Is there someway I can verify that? See below for the verions of dnsmasq: