topic PXE Boot Not Working in General Topics

PXE Boot Not Working

Bocsa — Mon, 03 Oct 2016 11:08:46 GMT

Hello everyone,

I have a new issue where a PA3020 has been placed between Client and Server subnets on the network. Since this install, building new PCs using PXE boot and deploying Applications using Windows SCCM no longer works.

The build starts and the client picks an IP address. On the logs, I can see successful traffic flows between Client and Server with application 'ms-sms' with Session End Reason 'tcp-fin'. So that stage seems fine. However afterwards, i start seeing TFTP traffic between both and this time the Session End Reason is 'aged-out'.

The traffic is being allowed through. And yes, tftp has been allowed in both directions on all ports.

Any thoughts or ideas please?

Thanks

Re: PXE Boot Not Working

bmorris1 — Mon, 03 Oct 2016 13:16:51 GMT

Hi Bocsa,

TFTP is UDP traffic, so if you allow this then the session end reason will nearly always be aged-out as it is connectionless.

Are you able to provide the detailed log view of the tftp traffic? You can grab this by clicking the spyglass on the left of the log.

You may need to run a packet capture of the flow to properly identify the cause of the issue.

Ben

Re: PXE Boot Not Working

Bocsa — Wed, 05 Oct 2016 08:48:11 GMT

Hi,

Detailed traffic view doesn't show much (attached).

Re: PXE Boot Not Working

_slv_ — Wed, 05 Oct 2016 12:28:09 GMT

Hello

If Your PC and WDS are in different network subnets You have to configure option 67 on DHCP serwer (on PC subnet)

Check this out:

https://community.spiceworks.com/topic/271704-windows-deployment-services-accross-subnets

Regards

SLawek

Re: PXE Boot Not Working

apfaff_adm — Sun, 04 Aug 2019 04:08:11 GMT

@_slv_ wrote:
Hello

If Your PC and WDS are in different network subnets You have to configure option 67 on DHCP serwer (on PC subnet)
Check this out:
https://community.spiceworks.com/topic/271704-windows-deployment-services-accross-subnets

Regards
SLawek

Or even better since using DHCP options for WDS isn't recommended as best practice anymore, add your WDS server to the list of DHCP servers in DHCP Relay. This won't work if the PA is your DHCP server.