PXE Immediately Giving WDS Error 0xc000000f

[txhockeyman]

So I find today that in trying to test a new TS that when booting PXE, I get an error screen from WDS that just only displays the error code 0xc000000f.

Digging around, I've found some that say it's a WDS problem and another that says it's an SSL issue because the MP is SSL but the DP is not.  One article states that if the MP is SSL, the DP also has to be using the PKI Cert as well instead of the self-signed. Another article mentions no problems with the DP being non-SSL.

This is what I'm seeing in SMSPXE.log

PXE::MP_GetList failed; 0x80070490    SMSPXE    5/16/2017 2:50:13 PM    5520 (0x1590)
PXE::MP_LookupDevice failed; 0x80070490    SMSPXE    5/16/2017 2:50:13 PM    5520 (0x1590)
PXE::MP_GetList failed; 0x80070490    SMSPXE    5/16/2017 2:50:13 PM    5520 (0x1590)
PXE::MP_ReportStatus failed; 0x80070490    SMSPXE    5/16/2017 2:50:13 PM    5520 (0x1590)
PXE Provider failed to process message. 
Element not found. (Error: 80070490; Source: Windows)    SMSPXE    5/16/2017 2:50:13 PM    5520 (0x1590)
 

Just looking for some insight on where to go with this.

 

Edited May 16, 2017 by txhockeyman
Added log snippet

[txhockeyman]

The issue was with SSL. The DP wasn't talking to the MP.  Even though a Microsoft article stated this was only a problem in 2012 RTM, seems it is still alive in Current Branch.