dhcp issue - Lenovo E73 - Realtek RTL8111GN

[pdit]

Our working FOG server is 1.5.4 version. isolated FOG server is 1.5.6 (one in question)

Here is Details about working FOG
Hardware : Lenovo M91p desktop
Running as VM in Vmware ESXi version:6.7.0
Desktop is connected to Linksys switch ( i sent you link about it earlier) which is than connects to Netgear managed switch.
DHCP is handled by MS windows server. Gateway is sophos firewall where options 66 & 67 are also setup.

we usually connect computers directly to Linksys switch where fog is connected and get them imaged.this is fastest way as transfer rate is much higher. sometimes we image them at some random location. but in both situation we have no issue imaging any type of computer. we maintain standard here so all our computers are of Lenovo brand. models are different and they changes every year. E73’s are the most in use here across offices.

The reason why we are setting up isolated FOG is to send it to our remote offices and get their computers imaged to win10. we tried doing this over WAN but failed. option 66 and 67 was setup correctly at one office but when computer boots up it doesn’t talk to FOG server which is here in our main office even though we have VPN tunnels in place.

Hope this helps. let me know if you need additional info.

[pdit]

i have setup new fog server identical to the one that is working with same hardware. everything is same except FOG version.and it still not working with E73 desktops. it is now proven that issue is not with E73 NIC but it’s FOG problem.

FOG Team, how can i get version 1.5.4 ? i am certain that this version of fog won’t give me trouble. Please help me get it.

[george1421]

@pdit I’m still not convinced its a fog issue here, but to answer your request you can get the 1.5.4 tarball here: https://github.com/FOGProject/fogproject/archive/1.5.4.tar.gz

[pdit]

I can confirm that the issue was in new FOG version. after i installed 1.5.4 version i am able to image same E73 desktops which didn’t work in new version. FOG team should look at what’s wrong in new version.

Thank you all for help. Please mark this resolve.

[Sebastian Roth]

@pdit So it’s probably something that changed in the Linux kernel that is causing this issue. I’d like to track this down but I don’t think I’ll find the time to do so in the next months.

You should be able to switch between different kernels to see which version first had the issue. Find all the different kernel versions in the FOG web UI or here: https://fogproject.org/kernels/