@george1421
Well I’ll be damned

@george1421 said in Finding messages or log from a failed pxe boot:

I little bit harder answer is to upgrade that windows 2008 server to something that is currently supported by Microsoft leaving this bad setting behind.

Yes, an upgrade of this DHCP server has been on the planning for a very long time but has always been delayed for al kinds of reasons. “it works and we have other priorities”

@george1421 said in Finding messages or log from a failed pxe boot:

Thinking out of the box installing dnsmasq configured as proxy dhcp server could fool the client into pxe booting too. Not ideal in the least but something that might work if all other things fail.

Yes I have been thinking about this, but that’s a serious hassle and will probably cause more issues than it solves…

I’ll leave it for now, upgrade the DHCP first and get back in touch if needed

@george1421

I have uninstalled the WDS service from the other server, double and triple checked and rebooted the DHCP server.

And option 60 is still being offered…

I’m lost…

@george1421

Thanks again, I did do a PCAP and I’m getting Option (60) Vendor class identier

This is not set by our DHCP, but we had WDS running in the past. The service is disabled, but I guess it is still answering…

To clearify: WDS was NOT installed on the DHCP server, but a separate server. That server is still running, but WDS is disabled.

In my search to figure out why my clients are not booting PXE I tried booting a virtual Win10 client.

On booting I got the warning “pxe-e55 proxydhcp service did not reply to request on port 4011”

Googling this, everywhere I read the suggestion to remove option 60 on my DHCP server. But option 60 is not set on my one and only DHCP server (Windows Server 2008R2). It’s not in the DHCP scope and not in the Server options.

I’m sorry but I don’t feel comfortable uploading the Wireshark captures as for now.

@george1421
it looks like my DHCP server does the OFFER with all required parameters:

@george1421

Yes, the computer (10.58.1.207) is on the same IP subnet as the fogserver (10.58.5.88)

I did do a pcap, but I’m a bit puzzled about this message:

Dynamic Host Configuration Protocol (Request)
    Message type: Boot Request (1)
    Hardware type: Ethernet (0x01)
    Hardware address length: 6
    Hops: 0
    Transaction ID: 0xd37bd5de
    Seconds elapsed: 3
        [Expert Info (Note/Protocol): Seconds elapsed appears to be encoded as little-endian]
            [Seconds elapsed appears to be encoded as little-endian]
            [Severity level: Note]
            [Group: Protocol]
    Bootp flags: 0x0000 (Unicast)
        0... .... .... .... = Broadcast flag: Unicast
        .000 0000 0000 0000 = Reserved flags: 0x0000
    Client IP address: 10.58.1.207
    Your (client) IP address: 0.0.0.0
    Next server IP address: 0.0.0.0
    Relay agent IP address: 0.0.0.0
    Client MAC address: a8:b1:3b:53:28:8e (a8:b1:3b:53:28:8e)
    Client hardware address padding: 00000000000000000000
    **Server host name not given
    Boot file name not given**

“Server host name not given” and “Boot file not given”

They are clearly set on the DCHP server.

Hi all, I’m very new to FOG and PXE. I set up a FOG server (Ubuntu) and I have added the options 66 (ip of the FOG server) and 67 (ipxe.efi) to my Windows DCHP server.

I’m trying to boot a laptop (HP Elitebook 840) over PXE in order to make an image of it.
When booting from XPE it says “Start PXE over IP4” but continues to boot to windows after a couple of seconds. If tried messing around with option 67, but no succes so far.

There are some messages showing between “Start pxe over ip4” and the windows boot animation. The problem is that these messages dissappear so quickly I can’t see what they say"

Is there way to see these message somewhere (log)?

Thanks in advance