Topics created by SBrady

@SBrady Looking at your pcap, you have 3 servers responding to the bootp request from your target computer. It appears the real dhcp server is at the .181 address and the 2 proxyDHCP servers are at .44 and .45. Both of the proxyDHCP servers are overriding what your main dhcp server is telling the target computer for where to get the boot file from.

I can’t tell from the proxyDHCP response what type of computer it is. The response doesn’t look like a Microsoft SCCM or WDS response because it is so short. I would focus on what .44 and .45 are and why they are responding to the bootp request.

Edit: Looking a bit more into the pcap there is also a WDS server responding to the DHCP DISCOVER query at the .217 address. That makes a total of 4 dhcp (and proxy servers responding) overriding what the main dhcp server was sending for dhcp options 66 and 67.

Here is a sanitized version of my unattend.xml file and how I call the sysprep. I used pretty much the same unattend.xml file with windows 10 deployments.

https://forums.fogproject.org/topic/11920/windows-10-1803-sysprep-problem/7

I might recommend that you build your reference image on a virtual machine so you can take snapshots to save the system state as important steps. This saves countless hours of having to start over from the beginning when something goes bad.

@SBrady said:

Which is better for Xen VM, guided or guided with LVM?

LVM is great if you know Linux well and can handle that complexity. If you don’t it might make things more prone to errors and I’d suggest installing without LVM.

@SBrady I myself have been bitten by web filter issues before on my linux FOG box, so no worries there haha! If you need any additional help or if you run into any other issues, please feel free to open another thread.

@george1421 Yea I tried to do the fdisk thing and also thought it was scary so stopped before I could do any damage. I might try again because I have a snapshot of the server so If I do anything I can just revert to the snapshot. I just wanted to be pointed in the right direction before I put time into it. I’m reading the first article you posted and if that doesn’t work I will try using fdisk. Thank you for replying, I’ll let you know what happens 🙂

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…

It doesn’t seem like it. When I enter the mySQL command from the terminal it gives the following error:

[B]Error 2002 (HY000): Can’t connect to local mySQL server through socket ’ /var/run/mysqld/mysqld.sock’ (2)[/B]

I cant get to the mysql command promt after it’s moved to the new subnet.

You could reinstall fog.

That will make a copy of your current /var/www/{html/,}fog folder in /var/www/fog.prev and place the contents of the default fog web folder in it’s relevant location.

[quote=“Tom Elliott, post: 28707, member: 7271”]It’s always the same file size?[/quote]

It was giving me different file sizes when I tried different Kernels. I was using .32 and just updated to 1.0.1. Now the Kernels are downloading but I can’t boot to the NIC. Did a setting get changed when I updated? Also, I noticed there is a new tftpboot folder and the old one was renamed to tftpboot.prev

Need some basic info.

What is running your DHCP services (FOG server, Windows, other appliance)?

Did you update your DHCP settings to include the PXE Boot info (next-server, filename, option 66 and 67)?

Is the client you’re trying to PXE boot in the same subnet and VLAN as your FOG server?

Can you get a picture of the screen with the pxe boot info and error messages, or a screen shot if you are using a VM?

I was able to add manually. Thank you