Post Reply 
 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Why I get this error 0xd126001 (http://ipxe.org/3d12001) using WDS?
2014-07-29, 15:36
Post: #1
Why I get this error 0xd126001 (http://ipxe.org/3d12001) using WDS?
I am new to windows server, I have two Machines, one with windows server 2008 and the other client one, I am trying to deploy windows to client using windows deployment services, I created the images, and get both booth and install. I put the client to boot from network, I configure my dhcp scope, but once I try to boot the client machine, I get the following error: tftp://10.10.10.1/reminst/Bootx86/Images/boot.wim .. Error 0x3d126001 (http://ipxe.org/3d126001) No more network devices

The boot image location is on //server/reminst/Bootx86/Images/boot.wim.

What is the wrong I do here, and how to solve this problem.
Find all posts by this user
Quote this message in a reply
2014-08-01, 15:13
Post: #2
RE: Why I get this error 0xd126001 (http://ipxe.org/3d12001) using WDS?
Based on the error code you copied it seems like your TFTP server is not responding properly to the URL you specified. It is known that the WDS TFTP server is a bit picky about using forward-slashes in paths, so you might need to use escaped backslashes (%5C). The URL should then look something like this: tftp://10.10.10.1/%5Creminst%5CBootx86%5CImages%5Cboot.wim

Although, if you're loading boot.wim directly I'm assuming you're using wimboot to load it. If that is the case, I'd load all of the files mentioned in http://ipxe.org/howto/winpe or http://ipxe.org/howto/sccm using HTTP URLs instead of TFTP. Microsoft IIS is much more standards-compliant than the WDS TFTP server.
Visit this user's website Find all posts by this user
Quote this message in a reply
2014-08-01, 18:49
Post: #3
RE: Why I get this error 0xd126001 (http://ipxe.org/3d12001) using WDS?
(2014-07-29 15:36)TakeruHiro Wrote:  I am new to windows server, I have two Machines, one with windows server 2008 and the other client one, I am trying to deploy windows to client using windows deployment services, I created the images, and get both booth and install. I put the client to boot from network, I configure my dhcp scope, but once I try to boot the client machine, I get the following error: tftp://10.10.10.1/reminst/Bootx86/Images/boot.wim .. Error 0x3d126001 (http://ipxe.org/3d126001) No more network devices

The boot image location is on //server/reminst/Bootx86/Images/boot.wim.

What is the wrong I do here, and how to solve this problem.

I think that you TFTP path has an error. I have myself a Windows Server too, and as far as I know, the "Reminst" folder is already the "root" folder of the TFTP server. I see another error regarding the x86 folder, you have forgotten a slash.

So, try using the path below:
tftp://10.10.10.1/Boot\x86\Images\boot.wim

The backslashes are defaults on Windows Server.
Find all posts by this user
Quote this message in a reply
Post Reply 




User(s) browsing this thread: 1 Guest(s)