1. Welcome Guest! In order to create a new topic or reply to an existing one, you must register first. It is easy and free. Click here to sign up now!.
    Dismiss Notice

pxe-e53 no bootfile name received

Discussion in 'Windows Home Server' started by alstar, Oct 5, 2009.

  1. alstar

    alstar Guest

    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 [​IMG]


    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:
    View this thread:

     
    alstar, Oct 5, 2009
    #1
  3. Tim Judd

    Tim Judd Guest

    alstar wrote:<!--coloro:blue--><span style="color:blue <!--/coloro-->
    > 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 [​IMG]
    >
    >
    > 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
    >
    > <!--colorc--><!--/colorc-->


    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
     
    Tim Judd, Oct 5, 2009
    #2
  4. alstar

    alstar Guest

    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:
    +-------------------------------------------------------------------+

    --
    alstar
    ------------------------------------------------------------------------
    alstar's Profile:
    View this thread:

     
    alstar, Oct 6, 2009
    #3
  5. alstar

    alstar Guest

    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:
    View this thread:

     
    alstar, Oct 6, 2009
    #4
  6. DaveMills

    DaveMills Guest

    On Tue, 6 Oct 2009 10:44:35 +0530, alstar <alstar.3zmd7b@DoNotSpam.com> wrote:
    <!--coloro:blue--><span style="color:blue <!--/coloro-->
    >
    >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...
    ><!--colorc--><!--/colorc-->
    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.

    <!--coloro:blue--><span style="color:blue <!--/coloro-->
    >
    >-A
    >
    >
    >+-------------------------------------------------------------------+
    >|Filename: ws.JPG |
    >|Download:
    >+-------------------------------------------------------------------+<!--colorc--><!--/colorc-->
    --
    Dave Mills
    There are 10 types of people, those that understand binary and those that don't.
     
    DaveMills, Oct 6, 2009
    #5
  7. alstar

    alstar Guest

    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:
    +-------------------------------------------------------------------+

    --
    alstar
    ------------------------------------------------------------------------
    alstar's Profile:
    View this thread:

     
    alstar, Oct 7, 2009
    #6
  8. DaveMills

    DaveMills Guest

    On Wed, 7 Oct 2009 10:59:27 +0530, alstar <alstar.3zoanb@DoNotSpam.com> wrote:
    <!--coloro:blue--><span style="color:blue <!--/coloro-->
    >
    >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<!--colorc--><!--/colorc-->

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

    <!--coloro:blue--><span style="color:blue <!--/coloro-->
    >
    >
    >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:
    >+-------------------------------------------------------------------+<!--colorc--><!--/colorc-->
    --
    Dave Mills
    There are 10 types of people, those that understand binary and those that don't.
     
    DaveMills, Oct 9, 2009
    #7

Share This Page