Jump to content


  • 0
Smytty

TFTP Access Violation Error when PXE booting

Question

Hi there folks, I have been having some issues getting a computer to properly PXE boot. This is on a new sccm setup on a server 2008 R2 box.

 

When I try to PXE the machine it gets an IP from my DHCP server ( since I added option 66 and 67 manually to my scope since my DHCP is on a seperate DC) but then it comes up with the following errors:

PXE-T04: Access Violation

PXE-E36: Error recived from TFTP Server

 

I have gone through the steps in this post to try and resolve it but to no avail. http://www.windows-noob.com/forums/index.php?/topic/546-how-can-i-troubleshoot-windows-pe-booting-in-sccm/

 

I have un-installed the pxe server role in SCCM, removed the WDS role from the server, rebooted, re-installed the WDS role and have not done any configuration to WDS and then re-setup the PXE role in SCCM. I have re-sent the boot files to my distribution point as well after this was done.

 

After all this I still recive the errors when I try to PXE boot and the following error shows up in my SMSPXE.log file:

 

Failed to read PXE settings.

The system cannot find the file specified. (Error: 80070002; Source: Windows) smspxe 2/23/2011 4:33:59 PM 768 (0x0300)

 

If anyone can shed anymore light on this and give me something else to try as I am completly stumped on this as to why I can not get this machine to PXE properly.

 

PS

 

I have also imported the machines MAC into SCCM and have it in a collection.

Share this post


Link to post
Share on other sites

3 answers to this question

Recommended Posts

  • 0

Hi there folks, I have been having some issues getting a computer to properly PXE boot. This is on a new sccm setup on a server 2008 R2 box.

 

When I try to PXE the machine it gets an IP from my DHCP server ( since I added option 66 and 67 manually to my scope since my DHCP is on a seperate DC) but then it comes up with the following errors:

PXE-T04: Access Violation

PXE-E36: Error recived from TFTP Server

 

I have gone through the steps in this post to try and resolve it but to no avail. http://www.windows-noob.com/forums/index.php?/topic/546-how-can-i-troubleshoot-windows-pe-booting-in-sccm/

 

I have un-installed the pxe server role in SCCM, removed the WDS role from the server, rebooted, re-installed the WDS role and have not done any configuration to WDS and then re-setup the PXE role in SCCM. I have re-sent the boot files to my distribution point as well after this was done.

 

After all this I still recive the errors when I try to PXE boot and the following error shows up in my SMSPXE.log file:

 

Failed to read PXE settings.

The system cannot find the file specified. (Error: 80070002; Source: Windows) smspxe 2/23/2011 4:33:59 PM 768 (0x0300)

 

If anyone can shed anymore light on this and give me something else to try as I am completly stumped on this as to why I can not get this machine to PXE properly.

 

PS

 

I have also imported the machines MAC into SCCM and have it in a collection.

 

 

check in WDS whether the boot files which you have mentioned are present ,under C:\RemoteInstall\ folder

Share this post


Link to post
Share on other sites

  • 0

Currently my "RemoteInstall" folder is residing on Drive F. I have gone through the process with WDS to change the location of the folder which has not helped either.

 

Currently under "F:\RemoteInstall\SMSIMAGES\SMSPKG\CO100001" There is a boot file located there.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.