I just want to say thank you for all the help! I am going to see if there is a switch laying around where I can test this. @JLE It’s on a completely different switch. I had a feeling it was some sort of issue regarding the switch just unsure what. Unfortunately I don’t have access to configuring the switches (apparently a third party does this??). I’ll get back to you guys one I can find a unmanaged switch switch, and tested it out.

@Sebastian-Roth Thank you for the reply! Sorry for late response; during the summer months of school people take a lot of vacation during this time.

I heard back from the technician over there, and she sent over screen shots, and here there are provided below.

HP 7800 Error Screen

Dell Optiplex 390 Error Screen

@george1421 Hey George, apologizes on the long response. I wanted to get more information regarding this, but the employee was gone on vacation.

The school is actually a direct connect, no VPN etc. Apparently we own that fiber as well. Regarding the random PC’s that boot, so far it’s only the GX520 desktop that’s able to boot into PXE. All of the schools that are connected to the main district are direct connect (something new I learned). Do you think this may be a switch issue?

@george1421 It’s at a remote location, and the PXE booting is random for sure. The ones that work at the moment are the Dell Optiplex GX520 desktops. I tested out the PXE at high school and the packet size is 1503. The 1503 packet size is what I am pulling here as well, where the server is at. Yikes…

@george1421 Yep, you’re right. No luck haha! Any other thoughts?

George,

Don’t know why it didn’t show up earlier, but here’s the code below. I did snoop through the forums and found this and tried to change the bootfile to ipxe.kpxe instead of undionly.kpxe. Still no luck with connecting.

https://forums.fogproject.org/topic/8449/ipxe-initialising-devices/3

PXEEBG PXENV at  PXE at  No PXE stack found
 entry point at 
         UNDI code segment  data segment  kB
         UNDI device is PCI          Unable to determine UNDI physical device type  workaround enabled         kB free base memory after PXE unload
         UNDI API call  failed status code 
PSUtG
u
XP XPtXffP
iXPXfQgfYfQP1gXfYfPfUfhfhfh0    jfh    jfjjffffnff
ffFhfV  fVf ffXfQSbrffTfffffYjdPPdXfVfWfUf1f1fffffff1fQfWfVf1ffVfffffSBfYfffhsPh4hPh0fuffffffffffPfufff
fsffXfWf4f
fgffWff1ff42PhfWSf286fa1GfVfMz
Installation failed  cannot continue```

Thank you for the reply! There is no firewall between the two subnets (that I know of) and it’s connected through a VLAN.

Here’s the filtered file here of the wireshark capture.
https://drive.google.com/file/d/0B1-vm6YfQDe1OFgzQUc5dEROTU0/view?usp=sharing

Server

• FOG Version: 1.4.3
• OS: 16.04 LTS

Client

• Service Version:
• OS: Windows 7, Dell Optiplex 390

Description

Hello,

I was wondering if anyone may help with resolving this? I currently have a FOG server running at the school (10.30.x.x), and it is working perfectly under that subnet. When it comes to different different VLANs, some devices can boot with PXE, and some cant. On the subnet that is 10.80.x.x the Dell computer won’t PXE boot, but when I bring the computer physically on this network it boots just fine in PXE. I did run Wireshark between the client and server, and it seems like it just keeps reading the file undionly.kpxe over and over until it times out. The firewalls are off on the FOG server to accept all traffic.

Any ideas?