@george1421 So now it finaly Works ! I am so Thankfull
I am now running some Deploys and Captures as a Test but so far it has the 5.6.18 Kernel and gets no Nic errors.

Just as an fyi the -o in your Command should be a Captial -O otherwise it creats just a .txt file and runs in an Format error at pxe boot.

But Again Thank you for the Support

@george1421 So actually we testet the ipxe.efi boot file and it Resolved the Error that we had. So thanks for the Help and Support, i hope it will stay so

@george1421 So we tested over a unmanaged Switch and this was the Result. So i think we need to dig deeper into the iPXE bot loader

@george1421 Thanks for the Answer, we updated the Kernel today.

Also we now have a new error with ipxe and AMD Mainboards/CPUs, can we discuss this in this thread or should i make a new one for this?

My assumption is that there is a problem with the DHCP-Bootfile

@george1421 So the unmanaged Switch fixet the Problem with the IP-Adresse.
I checked the STP mode on ouer Enterprise Switches (Cisco C3560G ) and it is on Rapid PVST, so rapid spanning tree.
Can there be another Reson why the Client dosent get an IP-Adress?

Also do you have an Kernel update Guid somwhere?
The Update on the FOG will be made by an Colleague and a Guid would be helpfull.

Thanks in Advance

@george1421 Thanks for the fast reply.

Here is the photo after entering the commands.

i will start the Kernel Update later this day, but after the command the Client got an IP-Adress and DNS-Server.

@george1421 Helo George1421,

here is a Picture of the Commands.

Also i also want to mention that the PXE Boot takes very long (about 3 Minutes) before the Client starts to boot into FOG.
Also it only Boots into FOG Weboverlay only without an Deploy process, with one it dosent Boot like seen in the Screenshot in my Original Post.

Kind Regards
Nick

Hello,

we have a FOG server for Imaging purposes and it Suddenly Stopt working for all ouer Notebooks.
You can boot into the FOG and start the Imgaing but after the Restart the following happens:

The FOG Server is in the same subnet withe the clients and we can Reach the FOG website.
FOG Version:1.5.8
Have you any Explanation for this behavior, all other Clients work normaliy in this Subnet and are Getting a DHCP-IP Adress.

Best Regards
Nick

@sebastian-roth Thanks again for the Answer, we nee to know this for Deployment of Snapins.

@sebastian-roth Thanks for the Response, is it than correct to assume the Client takes one of the dynamic Ports (49152 - 65535)?
And the Client Contacts always the Server and not the other way around?

Hello Forum,

how does the Client Communicate with the Server?
It says in the Wiki that the Client is Polling the Server, but on which Port ?
(https://wiki.fogproject.org/wiki/index.php?title=FOG_Client -> Polling Behavior)

At the end i need to know on what ports operates the client and on which the Server (The server probably on Port 80).

Thanks in advance for the answers.

@george1421 So now it finaly Works ! I am so Thankfull
I am now running some Deploys and Captures as a Test but so far it has the 5.6.18 Kernel and gets no Nic errors.

Just as an fyi the -o in your Command should be a Captial -O otherwise it creats just a .txt file and runs in an Format error at pxe boot.

But Again Thank you for the Support