PXE Problems booting to WDS Server

jcash101808@gmail.com

I am having a problem booting in a PXE environment to my WDS server.
I have VLANs I am working with. A machine in the same VLAN as the WDS
server works perfectly. However, a machine in a different VLAN shows
an error concerning a failure with the boot\bcd with a status of
0xc000000f and info that states an error occurred trying to read the
boot configuration data.

I looked in another post that prompted the user to replace the
pxeboot.com file in the DHCP option with the wdsnbp.com file, and had
no luck. I specifically used the wdsnbp.com file from the x86
architecture folder, but received a message that is was for x64
architecture.

I can't seem to get over this one obstacle. Any help out there?

Thanks

Rob Williamson

Tim Mintner \(MS\)

I would highly suggest going through this guide:
http://www.microsoft.com/downloads/d...displaylang=en

It specifically calls out the scenario that you are trying to support.

<jcash101808***********> wrote in message
news:1184696279.380526.227180@m37g2000prh.googlegr oups.com...
>I am having a problem booting in a PXE environment to my WDS server.
> I have VLANs I am working with. A machine in the same VLAN as the WDS
> server works perfectly. However, a machine in a different VLAN shows
> an error concerning a failure with the boot\bcd with a status of
> 0xc000000f and info that states an error occurred trying to read the
> boot configuration data.
>
> I looked in another post that prompted the user to replace the
> pxeboot.com file in the DHCP option with the wdsnbp.com file, and had
> no luck. I specifically used the wdsnbp.com file from the x86
> architecture folder, but received a message that is was for x64
> architecture.
>
> I can't seem to get over this one obstacle. Any help out there?
>
> Thanks
>
> Rob Williamson
>

Dan Van Drunen

Tim,
The link you provided is a great resource. To anyone looking into
implementing WDS, or any other 3rd party PXE solution this chm is worth a
read.
--
Dan Van Drunen
House of Commons, Canada


"Tim Mintner (MS)" wrote:

> I would highly suggest going through this guide:
> http://www.microsoft.com/downloads/d...displaylang=en
>
> It specifically calls out the scenario that you are trying to support.
>
> <jcash101808***********> wrote in message
> news:1184696279.380526.227180@m37g2000prh.googlegr oups.com...
> >I am having a problem booting in a PXE environment to my WDS server.
> > I have VLANs I am working with. A machine in the same VLAN as the WDS
> > server works perfectly. However, a machine in a different VLAN shows
> > an error concerning a failure with the boot\bcd with a status of
> > 0xc000000f and info that states an error occurred trying to read the
> > boot configuration data.
> >
> > I looked in another post that prompted the user to replace the
> > pxeboot.com file in the DHCP option with the wdsnbp.com file, and had
> > no luck. I specifically used the wdsnbp.com file from the x86
> > architecture folder, but received a message that is was for x64
> > architecture.
> >
> > I can't seem to get over this one obstacle. Any help out there?
> >
> > Thanks
> >
> > Rob Williamson
> >

Dan Van Drunen

Rob,
I am currently stuck at the exact same point as you are.
I have run into the following errors and were able to overcome them.

"DHCP...." followed by "PXE-E53: No boot filename received"
"TFTP...." followed by "PXE-E32: TFTP open timeout"
"TFTP...." followed by "PXE-T01: File not found"

Now I am receiving the sam error as you:
Title: Windows Boot Manager (Server IP: xxx.xxx.xxx.xxx)
Windows Failed to start...
File: \Boot\BCD
Status: 0xc000000f
Info: An error occurred while attempting to read the boot configuration data.

I verified that boot.sdi was in my wdsshare\boot folder.
The .wim image i added to boot from is what we are currently using on media
and works on all of our hardware.

--
Dan Van Drunen
House of Commons, Canada


"Dan Van Drunen" wrote:

> Tim,
> The link you provided is a great resource. To anyone looking into
> implementing WDS, or any other 3rd party PXE solution this chm is worth a
> read.
> --
> Dan Van Drunen
> House of Commons, Canada
>
>
> "Tim Mintner (MS)" wrote:
>
> > I would highly suggest going through this guide:
> > http://www.microsoft.com/downloads/d...displaylang=en
> >
> > It specifically calls out the scenario that you are trying to support.
> >
> > <jcash101808***********> wrote in message
> > news:1184696279.380526.227180@m37g2000prh.googlegr oups.com...
> > >I am having a problem booting in a PXE environment to my WDS server.
> > > I have VLANs I am working with. A machine in the same VLAN as the WDS
> > > server works perfectly. However, a machine in a different VLAN shows
> > > an error concerning a failure with the boot\bcd with a status of
> > > 0xc000000f and info that states an error occurred trying to read the
> > > boot configuration data.
> > >
> > > I looked in another post that prompted the user to replace the
> > > pxeboot.com file in the DHCP option with the wdsnbp.com file, and had
> > > no luck. I specifically used the wdsnbp.com file from the x86
> > > architecture folder, but received a message that is was for x64
> > > architecture.
> > >
> > > I can't seem to get over this one obstacle. Any help out there?
> > >
> > > Thanks
> > >
> > > Rob Williamson
> > >

jcash101808@gmail.com

Dan,

I noticed this in Chapter 5 of the documentation that Tim forwarded.

"However, if either the DHCP server or the network boot server are on
a different network segment than the client, or if they are on the
same network segment but the network is controlled by a switch or
router, it is usually necessary to update the networking equipment's
routing tables to ensure that DHCP traffic is directed appropriately.

This process is generally known as performing IP Helper table updates.
When performing this process, you must configure the networking
equipment so that all DHCP broadcasts from the client computer will be
directed to both a valid DHCP server and a valid network boot server.
(Note that the requirement is not to rebroadcast the packet onto other
network segments, but rather to perform a targeted forward of the
packet to only those recipients as listed in the IP Helper table.)

After the client computer has obtained its IP address, it contacts the
network boot server directly (again using DHCP packets) to obtain the
name and path of the network boot file to download. The specific
changes that need to be made are:

All DHCP broadcasts on UDP port 67 by client computers should be
forwarded directly to both the DHCP server and the Windows Deployment
Services PXE server.


All traffic to UDP port 4011 from the client computers to the Windows
Deployment Services PXE server is routed appropriately (these requests
direct traffic to the server, not broadcasts).


Updating the IP Helper tables is the approach that Microsoft
recommends for solving scenarios where the client computers and the
network boot server are not located on the same network segment."

The documentation also goes on to say that on some clients, it looks
for the boot program on the DHCP server, and not on the boot server
itself. This seems pretty consistent with what I am seeing, with the
process working with clients in the same network segment as the PXE
Server, but not on segments separated by a switch or router. We have
a highly granular structure to our network, everything separated by
VLANs. So, I am assuming that updating the IP Tables on the
equipment, not just the DHCP Scope Options may fix this problem. I am
not a network engineer or pro in the realm of PXE Deployment, but the
fact that the client can't read the boot configuration data seems to
point to this conclusion. I haven't verified it as a fix yet, I will
be working with the networking techs on this very soon.

Dan Van Drunen

Tim,
The link you provided is a great resource. To anyone looking into
implementing WDS, or any other 3rd party PXE solution this chm is worth a
read.
--
Dan Van Drunen
House of Commons, Canada


"Tim Mintner (MS)" wrote:

> I would highly suggest going through this guide:
> http://www.microsoft.com/downloads/d...displaylang=en
>
> It specifically calls out the scenario that you are trying to support.
>
> <jcash101808***********> wrote in message
> news:1184696279.380526.227180@m37g2000prh.googlegr oups.com...
> >I am having a problem booting in a PXE environment to my WDS server.
> > I have VLANs I am working with. A machine in the same VLAN as the WDS
> > server works perfectly. However, a machine in a different VLAN shows
> > an error concerning a failure with the boot\bcd with a status of
> > 0xc000000f and info that states an error occurred trying to read the
> > boot configuration data.
> >
> > I looked in another post that prompted the user to replace the
> > pxeboot.com file in the DHCP option with the wdsnbp.com file, and had
> > no luck. I specifically used the wdsnbp.com file from the x86
> > architecture folder, but received a message that is was for x64
> > architecture.
> >
> > I can't seem to get over this one obstacle. Any help out there?
> >
> > Thanks
> >
> > Rob Williamson
> >

Dan Van Drunen

Rob,
I am currently stuck at the exact same point as you are.
I have run into the following errors and were able to overcome them.

"DHCP...." followed by "PXE-E53: No boot filename received"
"TFTP...." followed by "PXE-E32: TFTP open timeout"
"TFTP...." followed by "PXE-T01: File not found"

Now I am receiving the sam error as you:
Title: Windows Boot Manager (Server IP: xxx.xxx.xxx.xxx)
Windows Failed to start...
File: \Boot\BCD
Status: 0xc000000f
Info: An error occurred while attempting to read the boot configuration data.

I verified that boot.sdi was in my wdsshare\boot folder.
The .wim image i added to boot from is what we are currently using on media
and works on all of our hardware.

--
Dan Van Drunen
House of Commons, Canada


"Dan Van Drunen" wrote:

> Tim,
> The link you provided is a great resource. To anyone looking into
> implementing WDS, or any other 3rd party PXE solution this chm is worth a
> read.
> --
> Dan Van Drunen
> House of Commons, Canada
>
>
> "Tim Mintner (MS)" wrote:
>
> > I would highly suggest going through this guide:
> > http://www.microsoft.com/downloads/d...displaylang=en
> >
> > It specifically calls out the scenario that you are trying to support.
> >
> > <jcash101808***********> wrote in message
> > news:1184696279.380526.227180@m37g2000prh.googlegr oups.com...
> > >I am having a problem booting in a PXE environment to my WDS server.
> > > I have VLANs I am working with. A machine in the same VLAN as the WDS
> > > server works perfectly. However, a machine in a different VLAN shows
> > > an error concerning a failure with the boot\bcd with a status of
> > > 0xc000000f and info that states an error occurred trying to read the
> > > boot configuration data.
> > >
> > > I looked in another post that prompted the user to replace the
> > > pxeboot.com file in the DHCP option with the wdsnbp.com file, and had
> > > no luck. I specifically used the wdsnbp.com file from the x86
> > > architecture folder, but received a message that is was for x64
> > > architecture.
> > >
> > > I can't seem to get over this one obstacle. Any help out there?
> > >
> > > Thanks
> > >
> > > Rob Williamson
> > >

jcash101808@gmail.com

Dan,

I noticed this in Chapter 5 of the documentation that Tim forwarded.

"However, if either the DHCP server or the network boot server are on
a different network segment than the client, or if they are on the
same network segment but the network is controlled by a switch or
router, it is usually necessary to update the networking equipment's
routing tables to ensure that DHCP traffic is directed appropriately.

This process is generally known as performing IP Helper table updates.
When performing this process, you must configure the networking
equipment so that all DHCP broadcasts from the client computer will be
directed to both a valid DHCP server and a valid network boot server.
(Note that the requirement is not to rebroadcast the packet onto other
network segments, but rather to perform a targeted forward of the
packet to only those recipients as listed in the IP Helper table.)

After the client computer has obtained its IP address, it contacts the
network boot server directly (again using DHCP packets) to obtain the
name and path of the network boot file to download. The specific
changes that need to be made are:

All DHCP broadcasts on UDP port 67 by client computers should be
forwarded directly to both the DHCP server and the Windows Deployment
Services PXE server.


All traffic to UDP port 4011 from the client computers to the Windows
Deployment Services PXE server is routed appropriately (these requests
direct traffic to the server, not broadcasts).


Updating the IP Helper tables is the approach that Microsoft
recommends for solving scenarios where the client computers and the
network boot server are not located on the same network segment."

The documentation also goes on to say that on some clients, it looks
for the boot program on the DHCP server, and not on the boot server
itself. This seems pretty consistent with what I am seeing, with the
process working with clients in the same network segment as the PXE
Server, but not on segments separated by a switch or router. We have
a highly granular structure to our network, everything separated by
VLANs. So, I am assuming that updating the IP Tables on the
equipment, not just the DHCP Scope Options may fix this problem. I am
not a network engineer or pro in the realm of PXE Deployment, but the
fact that the client can't read the boot configuration data seems to
point to this conclusion. I haven't verified it as a fix yet, I will
be working with the networking techs on this very soon.