• 0 Votes
    15 Posts
    5k Views
    G

    @george1421 @Tom-Elliott
    Luckily I could schedule a meeting with my System-Admin today, and he tried turning off the serving of the WDS boot file - seems in the configuration of option 66 and 67 of our companies DHCP server was an old Windows Server that served a meaningless WDS file, we changed it to my FOG Server and the issue is now solved.

    I am very thankful for your first-class support and I apologize for the inconvenience! You guys are my heroes!

  • 0 Votes
    16 Posts
    4k Views
    DarKFeeliND

    @george1421
    New revelations have been made. As I said I now replicated the whole setup on a local isolated network (with exception of the apparmor modifications, not necessary on a bare-metal installation).

    I have my witness-computer connected to both networks with 2 seperate NICs. Only one is active at a time. In both setups I first started wireshark on the witness computer and booted a notebook into pxe.

    Main network: No packets or barely some DHCP-ACKs (that were not from the booting laptop). Isolated local network: Discover -> Offer -> Request -> ACK. Laptop got an IP from the router and loaded the appropriate bootrom from the fogserver and booted from it.

    Conclusion: Since the witnessing of the DHCP-packets have nothing to do with fog itself it is safe to say that there is some sort of broadcoastfiltering of the DHCP-relevant ports. The (almost) exact same installation worked in an isolated network but not on the main network.

    Thank you so much, I finally know the exact cause of the problem and am able to proceed. I now have to write up a request if the networking team would be so kind to allow the broadcoasting of those port-packets to a single static IP that I own (I really hope they’ll allow that. Now that I think of it this makes total sense. If people are able to plug in their own devices into the network that behave like a DHCP-Server and then handle the IPs before the main DHCP does you are in a golden MITM-position and can intercept with the network-packets to your desire). But as far as fog goes, this is nothing from its side.

    So I think I can say this is solved for the cause of “troubleshooting”. Even if my journey is not exactly at its end yet. Thanks again!

  • Can't boot to PXE

    Solved FOG Problems
    40
    0 Votes
    40 Posts
    27k Views
    R

    Thank you all.
    I will update in case resolved.
    Take care!

  • Unable to Register Optiplex 780

    FOG Problems
    13
    0 Votes
    13 Posts
    6k Views
    Wayne WorkmanW

    We have some Lenovos that are weird.

    Pull the power cable and patch cable, hit the power button a few times, plug everything back up and auto-magically those weird ones start working…