pxe-e53 no bootfile name received

[alstar]

Hey Guys,

I have looked everywhere to reslove this problem that I have about a
client computer not being ale to boot in PXE so that WDS can deploy
W2K8.

I have checked forums and most of the blogs so this is like the last
restort asking myself

Alright my WDS was working and all of a sudden it stopped asssging Ip
addreesss and comes back with this error:

pxe-e53 no bootfile name received

I enabled DHCP options

060
066
067

No Go...

The computers are in the same subnet so that should not be an issue I
think.
Any ideas guys..


-A


--
alstar
------------------------------------------------------------------------
alstar's Profile: http://forums.techarena.in/members/141164.htm
View this thread: http://forums.techarena.in/windows-server-help/1254630.htm

http://forums.techarena.in

 

[Tim Judd]

alstar wrote:
> Hey Guys,
>
> I have looked everywhere to reslove this problem that I have about a
> client computer not being ale to boot in PXE so that WDS can deploy
> W2K8.
>
> I have checked forums and most of the blogs so this is like the last
> restort asking myself

>
>
> Alright my WDS was working and all of a sudden it stopped asssging Ip
> addreesss and comes back with this error:
>
> pxe-e53 no bootfile name received
>
> I enabled DHCP options
>
> 060
> 066
> 067
>
> No Go...
>
> The computers are in the same subnet so that should not be an issue I
> think.
> Any ideas guys..
>
>
> -A
>
>


I'd check:
Is the DHCP authoritative?
Does the DC(s) know about your Authoritative DHCP server?
Using a program like wireshark, does the DHCP negotiation offer these
options?
Is there a rogue DHCP server on the network?

I've noticed, on my own experimenting..
Remote Install Services doesn't need the DHCP options above.
Windows Deployment Services does, and only starts to work when a
image is successfully added to the Imaging server.



It seems that MS waits to setup these options until an image is added.

Please check the above.

--TJ

 

[alstar]

Hi,

Yeah my DHCP is authortaive and also there isnt any rogue dhcp.
I did use wire shark and I have attached the capture with this post as
I can see in that... a DHCP discover and offer is being made but the IP
is not assigned for some reason...

Any ideas guys...


-A


+-------------------------------------------------------------------+
|Filename: ws.JPG |
|Download: http://forums.techarena.in/attachment.php?...chmentid=10141|
+-------------------------------------------------------------------+

--
alstar
------------------------------------------------------------------------
alstar's Profile: http://forums.techarena.in/members/141164.htm
View this thread: http://forums.techarena.in/windows-server-help/1254630.htm

http://forums.techarena.in

 

[alstar]

From what I have read the error PXE-E53 No bootfilename recieved occurs
when the Ip is assigned but the client computer is unable to access the
PXE server for some reason....


I am running Windows2008 though and I also enabled the Reg key
"DisableRogueDetection" and the value to 0 ..that didnt help also...

-A


--
alstar
------------------------------------------------------------------------
alstar's Profile: http://forums.techarena.in/members/141164.htm
View this thread: http://forums.techarena.in/windows-server-help/1254630.htm

http://forums.techarena.in

 

[DaveMills]

On Tue, 6 Oct 2009 10:44:35 +0530, alstar wrote:

>
>Hi,
>
>Yeah my DHCP is authortaive and also there isnt any rogue dhcp.
>I did use wire shark and I have attached the capture with this post as
>I can see in that... a DHCP discover and offer is being made but the IP
>is not assigned for some reason...
>
>Any ideas guys...
>
This description is not consistent with your previous posting. Is the DHCP
server the same box as the WDS server?

The PXE client should get an IP before it report no boot file name.

It a while since I did a net trace on this but with separate DHCP/WDS servers it
should go a bit like

Client sends DHCP Discover
DHCP Server replied DHCP offer
Client Send DHCP Request
DHCP Server send DHCP Ack
and WDS sends DHCP Ack with the file name in it.

If the DHCP Server is the same as the WDS server then the name is in the Ack
with the IP lease.

Usually I see the PXE client report an IP address then report no filename.
Typically this is when the WDS BINL service is stopped.
I am not in front of a system right now so cannot check the correct names.


>
>-A
>
>
>+-------------------------------------------------------------------+
>|Filename: ws.JPG |
>|Download: http://forums.techarena.in/attachment.php?...chmentid=10141|
>+-------------------------------------------------------------------+
--
Dave Mills
There are 10 types of people, those that understand binary and those that don't.

 

[alstar]

Hi Dave,

Thanks for the reply.. I have the range of ip's defined under my WDS
server properties and I have attached a picture too so that u can see
it.

I am telling it not to use DHCP but use an internal range which I have
defined under the WDS server properties under the network settings tab

Use IP address from the following range

IPV4 from: 239.0.0.1 to 239.0.0.254


So in reality it shouldnt look for the dhcp but pick up adresses from
this range....


---------------------A test which I performed -------------

On my WDS server I created a DHCP scope and then used the MAC address
from my client machine and made a reservation and then tried the PXE
boot from the client (F12) and it worked and I was able to get to it..
but now I get another error message when I try and access the deployment
share where it asks for the network credentials.

It comes back with an error "Cannot connect to network share...path not
found"

The credentails are correct coz I tried it with various accounts and
also the distribution share has the proper permissions set ..for
Authenticated users"

----------------------



-A


+-------------------------------------------------------------------+
|Filename: dhcp.JPG |
|Download: http://forums.techarena.in/attachment.php?...chmentid=10156|
+-------------------------------------------------------------------+

--
alstar
------------------------------------------------------------------------
alstar's Profile: http://forums.techarena.in/members/141164.htm
View this thread: http://forums.techarena.in/windows-server-help/1254630.htm

http://forums.techarena.in

 

[DaveMills]

On Wed, 7 Oct 2009 10:59:27 +0530, alstar wrote:

>
>Hi Dave,
>
>Thanks for the reply.. I have the range of ip's defined under my WDS
>server properties and I have attached a picture too so that u can see
>it.
>
>I am telling it not to use DHCP but use an internal range which I have
>defined under the WDS server properties under the network settings tab
>
>Use IP address from the following range
>
>IPV4 from: 239.0.0.1 to 239.0.0.254

Ah you are using Multi cast. I have no experience of that as yet.


>
>
>So in reality it shouldnt look for the dhcp but pick up adresses from
>this range....
>
>
>---------------------A test which I performed -------------
>
>On my WDS server I created a DHCP scope and then used the MAC address
>from my client machine and made a reservation and then tried the PXE
>boot from the client (F12) and it worked and I was able to get to it..
>but now I get another error message when I try and access the deployment
>share where it asks for the network credentials.
>
>It comes back with an error "Cannot connect to network share...path not
>found"
>
>The credentails are correct coz I tried it with various accounts and
>also the distribution share has the proper permissions set ..for
>Authenticated users"
>
>----------------------
>
>
>
>-A
>
>
>+-------------------------------------------------------------------+
>|Filename: dhcp.JPG |
>|Download: http://forums.techarena.in/attachment.php?...chmentid=10156|
>+-------------------------------------------------------------------+
--
Dave Mills
There are 10 types of people, those that understand binary and those that don't.