PXE Windows Client registration

[krishna]

@george1421
66 on dhcp has the fog ip i.e. 192.168.172.10

[krishna]

@george1421
the screen capture is a random one from the web and got nothing to do with my fog environment.

thanks

[Sebastian Roth]

@krishna Using a random screenshot and not explain it costed you two days by pointing to the wrong direction. The clearer your information is the more we are able to help you.

OK, so this is a normal single master FOG node setup and we can rule out routing because FOG server and PXE booting clients are all in the same subnet?

So you have the firewall disabled in the FOG server?

Where clients ever able to PXE boot to the menu? If yes, when did it work last and what changed since then?

About the access.log - I just figured that Ubuntu moved to a different name at some point. Please run tail -f /var/log/apache2/*.log while you PXE boot one client to see if it shows up in the log.

[george1421]

This post is deleted!

[george1421]

This post is deleted!

[krishna]

@Sebastian-Roth

Here is the log output

tail -f /var/log/apache2/*.log
==> /var/log/apache2/access.log <==

==> /var/log/apache2/error.log <==
[Mon May 17 00:00:01.329479 2021] [mpm_prefork:notice] [pid 18103] AH00163: Apache/2.4.41 (Ubuntu) OpenSSL/1.1.1f configured – resuming normal operations
[Mon May 17 00:00:01.329494 2021] [core:notice] [pid 18103] AH00094: Command line: ‘/usr/sbin/apache2’

==> /var/log/apache2/other_vhosts_access.log <==
192.168.172.10:80 192.168.172.54 - - [17/May/2021:14:12:01 +0930] “POST /fog/service/ipxe/boot.php HTTP/1.1” 200 3388 “-” “iPXE/1.20.1+ (g4bd0)”

[Sebastian Roth]

@krishna said in PXE Windows Client registration:

==> /var/log/apache2/other_vhosts_access.log <==
192.168.172.10:80 192.168.172.54 - - [17/May/2021:14:12:01 +0930] “POST /fog/service/ipxe/boot.php HTTP/1.1” 200 3388 “-” “iPXE/1.20.1+ (g4bd0)”

Did that show up exactly at that Point in time when the client tried to load it? We see the client requesting the boot.php file for the FOG menu and it’s answered with a HTTP 200 status code. So it doesn’t seem to be an issue on the FOG server.

Does this happen with different hardware clients?

[krishna]

@george1421
@Sebastian-Roth

Hi, do you have any inputs on how to go about this ?

Cheers

[krishna]

@sebastian-roth
We only got HP Laptop hardware at the moment to test and all the devices reboot at this point and the FOG menu doesnt comeup at all,

Thanks

[Sebastian Roth]

@krishna Are these HP laptops different models?

I suggest you install tcpdump on your FOG server and capture network traffic so we might get more of an idea what’s happening: tcpdump -w /tmp/pxe_no_boot.pcap port 80 or port 67 or port 68 or port 69

Prepare this command and start up one of the laptops. Fire up the command and let it sit there (does not return to the command line). Let the laptop boot up to that point we see in the picture and then stop tcpdump (ctrl-c). Upload the captured PCAP file here in the forums or to an external fileshare and post a link.

[krishna]

@sebastian-roth
All the laptops we have are HP Probook x360 435 G7 model,

thanks