@Sebastian-Roth Well, the spanning tree reset did not work- and I’m pretty sure this is an internal problem with us having to do with switch configuration or how our vlan structures are set up. Thanks very much for your tips, I’m confident we have fog set up and working properly- only this one remote site has a config that we need to find and fix. Cheers guys and happy Friday!

@Sebastian-Roth Thank you for your response- we were short handed at work yesterday and I was hopping… Our admin is going to clear the cache on the switch tonight after faculty is done, and we’ll give 'er another shot!

@scott45426

@Wayne-Workman I’ve tried at our Jr. Hi site on many different machines, locations (and cables).
DHCP gets an address, opt66 / 67 are correct with server ip and boot file name.

iPxe initializing devices…ok.
Configuring (net0… reboot.
our adapters are pretty generic, you know- intel, realtek. The machines are a mixture of several years old, to brand new.

I completely realize this is probably not a “Fog” issue, but was hoping someone may have encountered the same problem as I am having.

I’m in a school district with five sites. I have fog imaging working across all the networks but one. In our Jr. Hi, my client computer will grab an ip, and start to boot with pxe, but fails during the network adapter configuration- ending with the machine rebooting itself. Confirmed with 3 different models of computer, and tested on all physical segments AND directly on each MC switch.

I’m not doing the network admin here, but all I can tell you is that our aruba controller and switches are “supposed” to be configured the same as our other four sites. The only difference I can see, is that our non-DC server at the Jr. Hi has 3 nics bridged (reason unknown).