Re: PXE Client could not get IP from DHCP Server

Yes, difference IP scope between RIS server and client PC.
Is there any specification about 66,67, I mean the parameters for reference.

Thanks
"swoodka" <swoodka@xxxxxxxxxxxxxxxxxxxxxxxxx> дÈëÏûÏ¢ÐÂÎÅ:780869B2-E0AE-499B-9620-C12D07C823BF@xxxxxxxxxxxxxxxx
Are the PC's that you are trying to PXE boot on the same subnet as the RIS
server?
The reason I as is that you will need to add options 66 and 67 to your
DHCP
Scope if they PCs ARE on a different subnet from your RIS and DHCP
servers.


"Microsoft News Group" wrote:

Hi,

The below is scenario for RIS and PXE client,

DC/DHCP, W2K3
RIS: Installed at another W2K3.
Client,OS:WinXP

DHCP is working very well, can assign IP for client PC after these PCs
logon
to domain.

In order to test RIS, I start one PC via NIC, PXE mode, but I am always
told
the following error:
no dhcp or proxydhcp offers were received

I searched Internet to get the following answers:

?
PXE-E51: No DHCP or proxyDHCP offers were received.
The client did not receive any valid DHCP, BOOTP or proxyDHCP
offers.
To resolve this issue, check each of the following network configuration
items:

?
DHCP services are not available on the network to which the
PXE-enabled NIC is connected.

?
A DHCP proxy or IP helper address is not configured for the
subnet on which the PXE client is connected.

?
The switch port connected to the PXE NIC is running Spanning
Tree
Protocol, EtherChannel Protocol, or Port Aggregation Protocol and is thus
not activated immediately when a link is detected. This forces the DHCP
request from the PXE client to timeout.

?
DHCP is available on the network, but PXE is not.

?
The network cable is not attached to the PXE-enabled NIC on
the
target server.



Interesting, this PC can get IP address after rebooting OS from
hard
disk.

Make sense please.

What's wrong in my operation and DHCP configuration.

BTW, some people said 60 class ID in DHCP configuration, is it
true?

Thanks,

DHCP Configuration
1.. Open the DHCP control panel from administrative tools.
2.. Expand the server you are wanting to configure. Expand the
"Scope" folder. Right click on "Scope Options" and select "Configure
Options".
3.. Put a check mark in "013 Boot File Size" and enter the file
size
in 512 octet blocks. Example, your boot image file is 12 KB (kilobytes).
Convert 12 KB to bytes (12288). This must be exact, don't just multiply
12
by 1000. Divide the file size in bytes by 512 (12288 / 512). Enter the
resulting number (24) in the text dialog that is enabled when you put a
check in 013.
4.. Put a check mark in "043 Vendor Specific Info" and enter the
following binary value: 01 04 00 00 00 00 ff.
5.. Open a command window and type the following:
6. c:\>netsh

7. netsh>dhcp

8. netsh dhcp>server \\server_name

9. netsh dhcp server>add optiondef 60 ClassID String 0

10. netsh dhcp server>set optionvalue 60 STRING PXEClient

11.. Put a check mark in "066 Boot Server Host Name" and enter
the
IP address of the server.
12.. Put a check mark in "067 Bootfile Name" and enter the name
of
the boot image file.
13.. (Thanks to Mark McRitchie for this step.)
If you use the Linux-based boot disk, you can set the boot disk's
defaults (user name, password, share) via DHCP option 233. Open a command
prompt and type:

netsh dhcp server add optiondef 233 Unattended String 0
comment="Unattended dhcp info"

Go back to "Scope Options", select configure options, put a check
mark
next to the new entry, and fill in the boot disk options you want to use
(e.g., z_user=username z_pass=sekrit z_path=\\myserver\myshare).

14.. Right click on the server name in the DHCP control panel, go
to
all tasks, and select "restart".
15.. Go back to scope options and verify that all the information
is
there. You should see the five entries on the right. They should look
like
this:
16.

17. 013 Boot File Size Standard 0x18

18. 043 Vendor Specific Info Standard 01 04 00
00
00 00 ff

19. 060 ClassID Standard PXEClient

20. 066 Boot Server Host Name Standard Server IP
address

21. 067 Bootfile Name Standard bzImage
(boot file name)

If any of the options do not match these, double-click on the
option
and change the value. More than likely option 060 will be wrong. Change
it
so it looks like above.







.

Relevant Pages

  • RE: Does RIS require a Microsoft DHCP server?
    ... Since I can't ever change that, I won't be able to use RIS since the DHCP ... server will point any PXE device, even a PC, at the phone server and the RIS ... What you do to authorize you RIS, if on another server, is open a DHCP MMC ...
    (microsoft.public.windows.server.general)
  • Re: Application Hang
    ... Back to DHCP, what about the client ipconfig without the DG ip address? ... When the old server crashed, it required a new motherboard and CPU. ... You should see at least,006 DNS servers, 003 Router. ...
    (microsoft.public.windows.server.networking)
  • RE: Does RIS require a Microsoft DHCP server?
    ... the benefits to running RIS on DHCP, ... What you do to authorize you RIS, if on another server, is open a DHCP MMC ...
    (microsoft.public.windows.server.general)
  • Re: Windows Server 2003 DHCP server - Does not release IP Addresses
    ... on the SWITCH or the ROUTER. ... the clients will not know which server to go for DHCP REQUEST. ... And, if that Switch had some issues, how will the other DHCP server ... This error is usually received when the client booting up via PXE is ...
    (microsoft.public.windows.server.general)
  • Re: DHCP handles Naks one one vlan differently
    ... If the problem is on the network with the DHCP server, ... Frame 156 ... Your (client) IP address: 0.0.0.0 ...
    (comp.dcom.sys.cisco)