Skip to main content

PXE-Server acting like a DHCP Proxy?!

Thread needs solution

Now I've read about alot of peopl ewith problems with PXE and not getting the PXE client to connect/load image...

I on the other hand have the opposite issue :D

Initially everything worked fine:
*Set up static leases in Microsoft DHCP with options 66/67 to point where it should point
*Machines so added was able to do a PXE boot
*Machines NOT added was not abel to boot from PXE

Just like my client wanted.

Then to solve the issue with the latest INTEL Network chipset I got the 584 build (Thanks Anna)

Things worked...too well...Now EVERY machine on the network was able to get the PXE boot menu.

Not good....

*Uninstall
*reboot
*cleaning out files
*reinstalling the 540 buil
*making damn sure that Option 66/67 was not set for the ANYTHING in the DHCP

Nope. As long as the acronis pxe-server is running it injects the options somehow.
It's allmost as it is running in some DHCP Proxy mode now.

If I disable the service/firewall port 67 UDP on the server running Snap Deploy, everything goes back to normal.

Of course, now I can't really USE Snap Deploy any more. So that kinda defeats the purpose :)

So to sum it all up...is there a way to turn off the Proxy like behavior ?

Or does anyone have any suggestions ?

0 Users found this helpful