Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Friday, March 20, 2015 1:23 PM
Hi,
I'm currently working on getting PXE working in dot1x. But first since this is the first time I'm working with SCCM (2012) and PXE deployments I wanted to get this working without dot1x. So I've done this:
Server-wise
- Setup a DP configured for PXE (99% sure this isn't the problem)
- Made boot images ready for deployment from the PXE-enabled DP (99% sure this isn't the problem)
--> Tested after this and got the PXE-E53. This is logical, I know, because I had no IP helper in place, neither DHCP scope options.
Network-wise
1. I went talking to someone from the network team and they said they didn't really like the IP helper, but they wanted to give it a try just for the testing phase. So he added an IP helper to the SCCM server.
--> Same error came up (PXE-E53)
2. Then he added DHCP scope options (66 & 67). 66 being the IP address of the SCCM server and 67 being SMSBoot\x86\wdsnbp.com.
--> Same error came up (PXE-E53)
3. I found someone on this site saying that the IP helper should go to the DP, not the SCCM server. So I asked the network guy to delete the DHCP scope options and set an IP helper to the PXE-enabled DP.
--> Again, same error came up (PXE-E53)
Am I missing something here? Any troubleshooting tips?
I tried to give as much information as I thought you guys would need, if more information is needed please ask. If you know an answer, may I ask to be as kind and really write it out so I can understand it. Massive SCCM/PXE noob (working with it my 5th week now).
Thanks in advance,
SanClo
All replies (22)
Friday, March 20, 2015 1:30 PM
Your IP helper needs to point to the system that has the PXE point. That might be a DP or it could be your site server, depends on your configuration.
Have you distributed the boot image to your distribution point/PXE point?
Is there anything in the smspxe.log?
Jeff
Friday, March 20, 2015 1:33 PM
IPhelpers have to point to the dhcp and pxe server.
Have you already examined smspxe.log?
Torsten Meringer | http://www.mssccmfaq.de
Friday, March 20, 2015 1:37 PM
I guess my SCCM server will be "the system that has the PXE point".
I have distributed the boot image.
I can't find the smspxe.log, I've checked in system32 and in \Program Files. I can nowhere find the log. I've searched my whole C drive for it, without any luck.
IP helpers pointing to the DHCP server and the DP now. They were pointing to the DHCP and SCCM server before but this didn't work.
Sander
Friday, March 20, 2015 1:53 PM | 1 vote
Help us out with how your environment is configured. . .you have a primary site server (the one you refer to as "the SCCM server")? Then you have a distribution point with PXE enabled?
smspxe.log will be on your PXE enabled DP. . .check the SMS_DP$\Logs folder. Also, here is a good log file reference:
https://technet.microsoft.com/en-us/library/hh427342.aspx#BKMK_SiteSiteServerLog
Jeff
Friday, March 20, 2015 1:54 PM
Also, if your IP helpers are now pointing to DHCP and the PXE-enabled DP, what are the results?
Jeff
Friday, March 20, 2015 2:06 PM
Yes, you're right. I got a primary site server (SCCM server) and 3 DP's (1 is PXE-enabled).
I have got IP helpers to the DHCP server and to the DP that is PXE-enabled. Still getting the PXE-E53 error with this setup.
Sorry to say but I still can't find the smspxe.log, I'm looking at the DP now and all I can see are the folders SMSBoot, SMSImages, SMSTemp, SMSTempBootFiles. Nowhere a Logs folder. I've shearched the server for "*.log" but this only gave a DPP.log. Will there be a log file if my client didn't talk to the PXE-enabled DP? Maybe he doesn't get there.
Sander
Friday, March 20, 2015 2:42 PM | 1 vote
Did you distribute both a 32-bit and 64-bit boot image to the distribution point?
Check out the TechNet documentation to make sure you have everything in place correctly: https://technet.microsoft.com/en-us/library/hh497405.aspx
Also, the folders you reference are WDS folders. . .the smspxe.log is in that SMS_DP$ folder. If it is not there, then there has not been PXE communication.
Jeff
Monday, March 23, 2015 7:38 AM
Hello,
One more to try is to install netmon on DP, capture DHCP protocol during PXE boot. You should see client is talking to DHCP server and PXE server. You will also see boot file name in the options.
If there is no problem with this process, please double check if all the package are distributed successfully.
And share smspxe.log.
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected].
Tuesday, March 24, 2015 8:07 AM
Yes, both boot images are distributed. That's what I was guessing aswell, that my client isn't getting to the PXE point. But he is getting an IP from DHCP.
I'll try the netmon on DP now and let you guys know what happened.
Big thank you for all the help.
Tuesday, March 24, 2015 8:40 AM
I installed the netmon on the PXE (SCCM) server, when I try to PXE-boot my client I don't get any logs on netmon. However, when I ping the PXE (SCCM) server, I do get logs of this.
Do I need to install the netmon on my DP2? If yes, any help on this?
Just another quick question. Environment:
PXE (SCCM) server
DP1
DP2 (PXE-enabled): both boot images distributed to this one
DP3
My IP helper is set to DP2, this is correct, right? Or does it needs to go to the PXE (SCCM) server?
And if I want to try with DHCP scope options, are the following options correct?
66: IP address of DP2
67: DPSERVERNAME reminst SMSBoot x64 wdsnbp . com
Tuesday, March 24, 2015 9:07 AM
Hi,
I meant to be the PXE-enabled DP which in case is DP2.
In addition, is this a UEFI module? Check BIOS setting, use legacy boot only.
At last, smspxe.log on site server will really be helpful to address the issue.
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected].
Tuesday, March 24, 2015 9:22 AM
I've updated the BIOS this morning, so this wouldn't be the problem I guess. I really don't have a smspxe.log on my server, I've looked everywhere and even used the search function on all the drives.
Tuesday, March 24, 2015 10:00 AM | 1 vote
Have you searched for smspxe.log on the pxe-enabled DP? It *must* be there.
Torsten Meringer | http://www.mssccmfaq.de
Tuesday, March 24, 2015 12:52 PM
I'm searching for it now; I RDC to the PXE (SCCM) server, open up a Windows Explorer, unfold the network tab, go to the PXE-enabled DP, I see this folder:
Reminst
I go in this folder, I see these folders:
Boot
Images
Mgmt
SMSBoot
SMSImages
SMSTemp
SMSTempBootFiles
Stores
Templates
Tmp
WdsClientUnattend
So nowhere the SMS_DP$ where the log file should be in. Isn't it possible there is no log file because of another error, I'm thinking the client being unable to connect to the DP?
Tuesday, March 24, 2015 1:01 PM
You won't see SMS_DP$ because it's a hidden share. Just search on the server directly. A folder called SMS_DP$ should be present in the root of the partition with the largest free disk space.
Torsten Meringer | http://www.mssccmfaq.de
Tuesday, March 24, 2015 1:13 PM
Finally, thank you guys for being as patient as you are.
SMSPXE.log
Date modified: 17/03/2015 (Tested it this morning so there is something wrong, no?)
17/03 I had an IP helper to the PXE (SCCM) server (my primary server). Still had the PXE-E53 tho.
<![LOG[Begin validation of Certificate [Thumbprint 49C3D9CE1B84207A2E18FC0ABC70E92C1D183514] issued to 'c116eb70-eb43-4d21-b4e1-2c698f77382a']LOG]!><time="12:24:36.068-60" date="03-17-2015" component="SMSPXE" context=""
type="1" thread="3144" file="ccmcert.cpp:1662">
<![LOG[Completed validation of Certificate [Thumbprint 49C3D9CE1B84207A2E18FC0ABC70E92C1D183514] issued to 'c116eb70-eb43-4d21-b4e1-2c698f77382a']LOG]!><time="12:24:36.068-60" date="03-17-2015" component="SMSPXE" context=""
type="1" thread="3144" file="ccmcert.cpp:1803">
<![LOG[PXEClientKey certificate valid.]LOG]!><time="12:24:36.068-60" date="03-17-2015" component="SMSPXE" context="" type="1" thread="3144" file="certhdl.cpp:174">
<![LOG[Purging old images: 0]LOG]!><time="12:24:42.370-60" date="03-17-2015" component="SMSPXE" context="" type="1" thread="3144" file="bootimagemgr.cpp:1647">
<![LOG[Purging old images: 0]LOG]!><time="12:34:42.397-60" date="03-17-2015" component="SMSPXE" context="" type="1" thread="4872" file="bootimagemgr.cpp:1647">
<![LOG[Purging old images: 0]LOG]!><time="12:44:42.423-60" date="03-17-2015" component="SMSPXE" context="" type="1" thread="1624" file="bootimagemgr.cpp:1647">
<![LOG[Purging old images: 0]LOG]!><time="12:54:42.450-60" date="03-17-2015" component="SMSPXE" context="" type="1" thread="3000" file="bootimagemgr.cpp:1647">
<![LOG[Purging old images: 0]LOG]!><time="13:04:42.476-60" date="03-17-2015" component="SMSPXE" context="" type="1" thread="3992" file="bootimagemgr.cpp:1647">
<![LOG[Purging old images: 0]LOG]!><time="13:14:42.503-60" date="03-17-2015" component="SMSPXE" context="" type="1" thread="3132" file="bootimagemgr.cpp:1647">
<![LOG[Begin validation of Certificate [Thumbprint 49C3D9CE1B84207A2E18FC0ABC70E92C1D183514] issued to 'c116eb70-eb43-4d21-b4e1-2c698f77382a']LOG]!><time="13:24:36.180-60" date="03-17-2015" component="SMSPXE" context=""
type="1" thread="3708" file="ccmcert.cpp:1662">
<![LOG[Completed validation of Certificate [Thumbprint 49C3D9CE1B84207A2E18FC0ABC70E92C1D183514] issued to 'c116eb70-eb43-4d21-b4e1-2c698f77382a']LOG]!><time="13:24:36.180-60" date="03-17-2015" component="SMSPXE" context=""
type="1" thread="3708" file="ccmcert.cpp:1803">
<![LOG[PXEClientKey certificate valid.]LOG]!><time="13:24:36.180-60" date="03-17-2015" component="SMSPXE" context="" type="1" thread="3708" file="certhdl.cpp:174">
<![LOG[Purging old images: 0]LOG]!><time="13:24:42.529-60" date="03-17-2015" component="SMSPXE" context="" type="1" thread="3708" file="bootimagemgr.cpp:1647">
<![LOG[Purging old images: 0]LOG]!><time="13:34:42.555-60" date="03-17-2015" component="SMSPXE" context="" type="1" thread="3496" file="bootimagemgr.cpp:1647">
<![LOG[Purging old images: 0]LOG]!><time="13:44:42.582-60" date="03-17-2015" component="SMSPXE" context="" type="1" thread="5116" file="bootimagemgr.cpp:1647">
<![LOG[Purging old images: 0]LOG]!><time="13:54:42.608-60" date="03-17-2015" component="SMSPXE" context="" type="1" thread="1028" file="bootimagemgr.cpp:1647">
<![LOG[Purging old images: 0]LOG]!><time="14:04:42.635-60" date="03-17-2015" component="SMSPXE" context="" type="1" thread="2396" file="bootimagemgr.cpp:1647">
<![LOG[Purging old images: 0]LOG]!><time="14:14:42.661-60" date="03-17-2015" component="SMSPXE" context="" type="1" thread="3608" file="bootimagemgr.cpp:1647">
<![LOG[Begin validation of Certificate [Thumbprint 49C3D9CE1B84207A2E18FC0ABC70E92C1D183514] issued to 'c116eb70-eb43-4d21-b4e1-2c698f77382a']LOG]!><time="14:24:36.291-60" date="03-17-2015" component="SMSPXE" context=""
type="1" thread="4780" file="ccmcert.cpp:1662">
<![LOG[Completed validation of Certificate [Thumbprint 49C3D9CE1B84207A2E18FC0ABC70E92C1D183514] issued to 'c116eb70-eb43-4d21-b4e1-2c698f77382a']LOG]!><time="14:24:36.291-60" date="03-17-2015" component="SMSPXE" context=""
type="1" thread="4780" file="ccmcert.cpp:1803">
<![LOG[PXEClientKey certificate valid.]LOG]!><time="14:24:36.291-60" date="03-17-2015" component="SMSPXE" context="" type="1" thread="4780" file="certhdl.cpp:174">
<![LOG[Purging old images: 0]LOG]!><time="14:24:42.688-60" date="03-17-2015" component="SMSPXE" context="" type="1" thread="4780" file="bootimagemgr.cpp:1647">
<![LOG[Cannot read the registry value of MACIgnoreListFile (00000000)]LOG]!><time="14:24:52.438-60" date="03-17-2015" component="SMSPXE" context="" type="1" thread="4780" file="provsettings.cpp:353">
<![LOG[MAC Ignore List Filename in registry is empty]LOG]!><time="14:24:52.438-60" date="03-17-2015" component="SMSPXE" context="" type="1" thread="4780" file="provsettings.cpp:468">
<![LOG[Cannot read the registry value of MACIgnoreListFile (00000000)]LOG]!><time="14:26:52.484-60" date="03-17-2015" component="SMSPXE" context="" type="1" thread="1828" file="provsettings.cpp:353">
<![LOG[MAC Ignore List Filename in registry is empty]LOG]!><time="14:26:52.484-60" date="03-17-2015" component="SMSPXE" context="" type="1" thread="1828" file="provsettings.cpp:468">
<![LOG[================= PXE Provider shutdown. =====================]LOG]!><time="14:29:08.926-60" date="03-17-2015" component="SMSPXE" context="" type="1" thread="2636" file="smspxe.cpp:223">
I've checked the following with the network monitor:
- Ping to the DP: works
- PXE boot: nothing comes up (But got an IP helper to it?)
- Downloaded a DHCP test tool, nothing comes up. --> Is my IP helper wrong? (set to PXE-enabled DP)
Thursday, March 26, 2015 9:15 AM
Anyone got some ideas?
Sander
Thursday, March 26, 2015 9:30 AM
Is my IP helper wrong? (set to PXE-enabled DP)
This is what an IP Helper should look like.
Here is an example from a Cisco switch:
interface Vlan10
ip address 172.16.112.254 255.255.255.0
ip helper-address 172.16.1.1
End
This allows clients booting in 172.16.112.0/24 subnet to find the PXE enabled DP (172.16.1.1).
Gerry Hampson | Blog: www.gerryhampsoncm.blogspot.ie | LinkedIn: Gerry Hampson | Twitter: @gerryhampson
Thursday, March 26, 2015 10:00 AM
That's exactly how the IP helper is set.
Example of the setup I'm using;
interface vlan 602
ip address [SUBNET OF THE SERVERS]
ip helper-address [DHCP IP ADDRESS]
ip helper-address [PXE-ENABLED DP]
end
But still I'm unable to PXE boot.
I asked the network team to set the option 66 en 67 again on DHCP. When this was enabled I had logs in the SMSPXE.log, but still got PXE-E53. I'll report back when this is done and I've done some tests.
Sander
Tuesday, April 7, 2015 9:06 AM
I've made a new question with additional info in. https://social.technet.microsoft.com/Forums/en-US/0c7774c0-1171-4102-935f-cea242795482/error-pxee53-no-boot-filename-received?forum=configmanagerosd
Can anyone help?
Sander
Friday, August 28, 2015 6:29 PM
Were you able to solve your problem. I am having the same issue.
Saturday, August 29, 2015 2:53 AM | 1 vote
Please look at the SMSPXE.log file on the PXE DP.
You should find the logs lines for the MAC address of the client that is trying to PXE boot.
If you don't find such log lines, it means that the DHCP boot request packets from the client is not reaching the PXE DP, which means that your IP Helper is not doing its job. You should be able to confirm that with some network trace.