PXE and DHCP

What options do I need to set on DHCP running on Win2K3
server to allow PXE clients that I will be imaging? Thanks.

Hmmm...at the risk of sounding like an idiot....what's a PXE client?


--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


"Parhez Sattar" <(E-Mail Removed)> wrote in message
news:12c5401c4433c$129cc820$(E-Mail Removed)...
> What options do I need to set on DHCP running on Win2K3
> server to allow PXE clients that I will be imaging? Thanks.

Many NICs now come with PXE (Pre-Execution Environment)
feature. It is a protocol designed by Intel that allows
computers to boot through the network. PXE is stored in
the ROM of new generation network cards. When the computer
boots up, the BIOS loads the PXE ROM in the memory and
executes it. A menu is displayed, allowing the computer to
boot an operating system loaded through the network. PXE
has been around for a long time, but is becoming more
popular recently. If you bought your NIC in the last 3
years, chances are it supports PXE.

Hope this helps.





>-----Original Message-----
>Hmmm...at the risk of sounding like an idiot....what's a
PXE client?
>
>
>--
>
>Phillip Windell [MCP, MVP, CCNA]
>www.wandtv.com
>
>
>"Parhez Sattar" <(E-Mail Removed)> wrote in message
>news:12c5401c4433c$129cc820$(E-Mail Removed)...
>> What options do I need to set on DHCP running on Win2K3
>> server to allow PXE clients that I will be imaging?
Thanks.
>
>
>.
>

Ok. Well I suspect it is going to be up to PXE to implement DHCP queries
properly. In other words it is up to PXE to do it "right" to work with
DHCP,...it is not going to be up to DHCP to do it PXE's way. The DHCP
Server wouldn't know or even care if it was a PXE"bootup" of a regular
"bootup".....a DHCP query is just a DHCP query, it will answer it the way it
would any query.

DHCP is an industry standard, so it is up to engineers to design their
product to work with the industry standards.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


"Parhez Sattar" <(E-Mail Removed)> wrote in message
news:12f9401c4434d$006ddfc0$(E-Mail Removed)...
> Many NICs now come with PXE (Pre-Execution Environment)
> feature. It is a protocol designed by Intel that allows
> computers to boot through the network. PXE is stored in
> the ROM of new generation network cards. When the computer
> boots up, the BIOS loads the PXE ROM in the memory and
> executes it. A menu is displayed, allowing the computer to
> boot an operating system loaded through the network. PXE
> has been around for a long time, but is becoming more
> popular recently. If you bought your NIC in the last 3
> years, chances are it supports PXE.
>
> Hope this helps.
>
>
>
>
>
> >-----Original Message-----
> >Hmmm...at the risk of sounding like an idiot....what's a
> PXE client?
> >
> >
> >--
> >
> >Phillip Windell [MCP, MVP, CCNA]
> >www.wandtv.com
> >
> >
> >"Parhez Sattar" <(E-Mail Removed)> wrote in message
> >news:12c5401c4433c$129cc820$(E-Mail Removed)...
> >> What options do I need to set on DHCP running on Win2K3
> >> server to allow PXE clients that I will be imaging?
> Thanks.
> >
> >
> >.
> >

I am not concerned about having the PXE client working
with the DHCP server, as when you set the client BIOS to
boot using PXE, it will look for a DHCP server and find it
through DHCP broadcasts. However, how would it know what
server to contact to get the image and also which image to
choose, even after the DHCP server gives it an IP address,
using which it will contact the other servers/services?

From my research so far, I may have to set the options
060, 066, 067, 043 and use the appropriate values within
those option on my DHCP server. Can anyone verify this,
please?






>-----Original Message-----
>Ok. Well I suspect it is going to be up to PXE to
implement DHCP queries
>properly. In other words it is up to PXE to do
it "right" to work with
>DHCP,...it is not going to be up to DHCP to do it PXE's
way. The DHCP
>Server wouldn't know or even care if it was a PXE"bootup"
of a regular
>"bootup".....a DHCP query is just a DHCP query, it will
answer it the way it
>would any query.
>
>DHCP is an industry standard, so it is up to engineers to
design their
>product to work with the industry standards.
>
>--
>
>Phillip Windell [MCP, MVP, CCNA]
>www.wandtv.com
>
>
>"Parhez Sattar" <(E-Mail Removed)> wrote in message
>news:12f9401c4434d$006ddfc0$(E-Mail Removed)...
>> Many NICs now come with PXE (Pre-Execution Environment)
>> feature. It is a protocol designed by Intel that allows
>> computers to boot through the network. PXE is stored in
>> the ROM of new generation network cards. When the
computer
>> boots up, the BIOS loads the PXE ROM in the memory and
>> executes it. A menu is displayed, allowing the computer
to
>> boot an operating system loaded through the network.
PXE
>> has been around for a long time, but is becoming more
>> popular recently. If you bought your NIC in the last 3
>> years, chances are it supports PXE.
>>
>> Hope this helps.
>>
>>
>>
>>
>>
>> >-----Original Message-----
>> >Hmmm...at the risk of sounding like an idiot....what's
a
>> PXE client?
>> >
>> >
>> >--
>> >
>> >Phillip Windell [MCP, MVP, CCNA]
>> >www.wandtv.com
>> >
>> >
>> >"Parhez Sattar" <(E-Mail Removed)> wrote in message
>> >news:12c5401c4433c$129cc820$(E-Mail Removed)...
>> >> What options do I need to set on DHCP running on
Win2K3
>> >> server to allow PXE clients that I will be imaging?
>> Thanks.
>> >
>> >
>> >.
>> >
>
>
>.
>

http://support.microsoft.com/default...b;EN-US;244036
Description of PXE Interaction Among PXE Client, DHCP, and RIS Server

http://support.microsoft.com/?kbid=259670
Using DHCP Options 60, 66, 67 to Direct PXE Clients to RIS Servers May Fail

When the machine boots using PXE, the boot ROM gets an IP address using
DHCP. It's then sending out a modified DHCP Discover packet with its GUID.
The BINL service on a RIS server listens for these special DHCP Discover
packets and responds with a DHCP Offer packet that includes a copy of the
client's GUID, but no IP address. The PXE client replies with a DHCP Request
packet sent directly to the BINL service on UDP port 4011. The BINL service
responds with a DHCP Ack packet that contains the name and path of the boot
image, startrom.com.
In a routed network, an IP helper field in the router contains the IP
address of a DHCP server. When the router receives a DHCP Discover packet,
it forwards the packet to the DHCP server and then acts as an intermediary
between the server and the DHCP client. If the RIS server is also a DHCP
server, this works fine. The server returns a single DHCP Offer packet with
the client's GUID in the payload and the client handles the rest. If the
DHCP server and RIS server are on different machines in the same broadcast
segment as the PXE client, the process also proceeds without problems.
If, however, the RIS server and the DHCP server are on different machines
that don't reside in the same broadcast segment as the PXE client, both
servers must be included in the IP helper field at the router, and you must
verify that both servers get the DHCP Discover packet from the router.
If you have more than one RIS server, don't install RIS on a DHCP server. A
PXE client that gets a standard DHCP Offer that contains its GUID won't
listen for responses from any other RIS servers.
Because BINL is actually a modified DHCP service, it must be authorized in
AD.

Excellent! I'll have to keep a copy of those links.


--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


"Jetro" <no.spam@internet> wrote in message
news:ObMIPF%(E-Mail Removed)...
> http://support.microsoft.com/default...b;EN-US;244036
> Description of PXE Interaction Among PXE Client, DHCP, and RIS Server
>
> http://support.microsoft.com/?kbid=259670
> Using DHCP Options 60, 66, 67 to Direct PXE Clients to RIS Servers May
Fail
>
> When the machine boots using PXE, the boot ROM gets an IP address using
> DHCP. It's then sending out a modified DHCP Discover packet with its GUID.
> The BINL service on a RIS server listens for these special DHCP Discover
> packets and responds with a DHCP Offer packet that includes a copy of the
> client's GUID, but no IP address. The PXE client replies with a DHCP
Request
> packet sent directly to the BINL service on UDP port 4011. The BINL
service
> responds with a DHCP Ack packet that contains the name and path of the
boot
> image, startrom.com.
> In a routed network, an IP helper field in the router contains the IP
> address of a DHCP server. When the router receives a DHCP Discover packet,
> it forwards the packet to the DHCP server and then acts as an intermediary
> between the server and the DHCP client. If the RIS server is also a DHCP
> server, this works fine. The server returns a single DHCP Offer packet
with
> the client's GUID in the payload and the client handles the rest. If the
> DHCP server and RIS server are on different machines in the same broadcast
> segment as the PXE client, the process also proceeds without problems.
> If, however, the RIS server and the DHCP server are on different machines
> that don't reside in the same broadcast segment as the PXE client, both
> servers must be included in the IP helper field at the router, and you
must
> verify that both servers get the DHCP Discover packet from the router.
> If you have more than one RIS server, don't install RIS on a DHCP server.
A
> PXE client that gets a standard DHCP Offer that contains its GUID won't
> listen for responses from any other RIS servers.
> Because BINL is actually a modified DHCP service, it must be authorized in
> AD.
>
>