SOLVED Config Manager PXE Responder Wont Start

[tom.allen]

Hi All,

long time lurker, first timer poster!

Since upgrading to Endpoint Manager 2002 I cannot get anything to PXE boot, on closer inspection the Config Manager PXE Responder Service is started, but the SMSPXE log shows it hanging at 'Starting TFTP' which it won't get past:

Start SCCM PXE as a service. SCCMPXE 03/06/2020 12:35:35 10728 (0x29E8)
ServiceMain() SCCMPXE 03/06/2020 12:35:35 3116 (0x0C2C)
Starting sccmpxe.exe version 5.0.8968.1000 from location 'E:\Program Files\Microsoft Configuration Manager\bin\x64\sccmpxe.exe' SCCMPXE 03/06/2020 12:35:35 3116 (0x0C2C)
Firewall service is already running. SCCMPXE 03/06/2020 12:35:35 3116 (0x0C2C)
Module folder: E:\Program Files\Microsoft Configuration Manager\bin\x64 SCCMPXE 03/06/2020 12:35:35 3116 (0x0C2C)
ControlService() returned 0x80070426 when stopping the WDS service. SCCMPXE 03/06/2020 12:35:35 3116 (0x0C2C)
PXE: HPCSCCM01, HPCSCCM01.schools.local SCCMPXE 03/06/2020 12:35:35 3116 (0x0C2C)
--- Starting DHCP on 00:50:56:82:02:08, 10.101.56.227, 67. SCCMPXE 03/06/2020 12:35:36 3116 (0x0C2C)
--- Starting PXE on 00:50:56:82:02:08, 10.101.56.227, 4011. SCCMPXE 03/06/2020 12:35:36 3116 (0x0C2C)
--- Starting TFTP on 10.101.56.227. SCCMPXE 03/06/2020 12:35:36 4864 (0x1300)

I have no component errors in SCCM, everything is green. I have a single Distrtibution Point and Management Point environment, all on the one server. I have tried removing and readding PXE from the distribution point settings and rebooting between to no avail.

Any ideas?

Thanks

 

[Prajwal Desai]

Control service returned 0x80070426 when stopping the WDS service - Is WDS servicing also running on that server ?.

 

[tom.allen]

The service is installed, but isn't running (disabled)

 

[Prajwal Desai]

And I hope you have disabled the Multicast feature on the DP ?.

 

[tom.allen]

Yes multicast is not checked in DP options.

 

[Prajwal Desai]

Ok, can you share smspxe.log file. I am still not sure why this message appears - ControlService() returned 0x80070426 when stopping the WDS service.

 

[tom.allen]

Thanks, file attached , there are some errors in there that relate to WDS, this is from when I removed and readded PXE on the DP earlier today.

 

[Prajwal Desai]

PXE: bind() failed for DHCP, 00:50:56:82:02:08, 10.101.56.227, port 67. 0x80072740. Another process (DHCP server or PXE server) is already using the port - Check on the DHCP options and ensure the port 67 is not used by another process.

When you enable a PXE responder on a distribution point without Windows Deployment Service, it can now be on the same server as the DHCP service. Add the following settings to support this configuration:

• Set the DWord value DoNotListenOnDhcpPort to 1 in the following registry key: HKLM\Software\Microsoft\SMS\DP.
• Set DHCP option 60 to PXEClient.
• Restart the SCCMPXE and DHCP services on the server.

 

[tom.allen]

Yeah that was from when I was messing with it earlier, I'd tried to start it manually to see if it gave any more clues but I'd tried whilst it was running, hence the binding error.

I think however I may have sorted it. Immediately after upgrade to 2002 I tried to PXE boot something and got no response, so that's what started me down this whole road, I had some cert errors in the PXE log last week which I sorted by changing the date on the cert the DP uses to get it to regenerate it. Those went away, but I swear it used to say 'PXE Service Started' in that log, I wasn't seeing that so assumed it wasn't working> I have actually just tried PXE booting a VM on the same subnet and its working. Nothing has changed as far as the IP helpers go, so fingers crossed when I try a physical machine on a different subnet tomorrow, it will work.

I'll let you know!

 

[tom.allen]

Yep tried a physical machine on a different VLAN and it’s working. So it was the certificate errors initially. I swear it deffo used to say ‘PXE service started’ in that log though! One to watch out for I guess. Thanks pal.