@Sebastian-Roth

I’ll have to brush up on the commands for replacing the certs on the clients. Been a long time.

Thanks for your response @Daniel-Miller! It looks like I overlooked this plugin; it seems to be generally what I am looking for. There definitely seems to be issues related to provisioning with plugins (as has already been mentioned in the link you shared). Currently I can either have the printers auto-add using the persistent group and have snapins not run (which essentially breaks the provisioning process) or I can have Snapins run but not use the persistent group.

I have run at least a test or two where I think I got both to work but it may have been a fluke as I can’t really replicate that. I will keep plugging along.

Thanks for pointing me in the right direction!

@Dv27842 said in Unable to change IP for FOG Server installation on Ubuntu Server 18.04:

I have tried to change the IP address to a static IP address that is currently on my sandbox, but it will not keep the changes

Please give us more details. Where exactly did you try to change the IP? Within Ubuntu? Which file did you edit? What did it look like before?

I can imagine you were editing the wrong file. Ubuntu 16.04 network config is different than Ubuntu 18.04, see here: https://www.ostechnix.com/how-to-configure-ip-address-in-ubuntu-18-04-lts/

@tiengdung90 Can’t help you without further information.

@Greg-Plamondon Is this still an issue or did you find what was causing this?

@sgoodman Bump…

@sgoodman @Daniel-Miller @Greg-Plamondon @george1421 Has anyone run into this issue (again)? I’d think this might have been caused by a major .NET framework update which we can’t do much about.

In case people have PCs running for a long time without restart they might consider setting the service to auto-restart.

I am marking this solved now. Feel free to post if you think it’s not.

Cross reference to another topic: https://forums.fogproject.org/topic/13704/fog-service-quits-running

@Matthieu-Jacquart Sure right. If one client was pinned to the re-newed server CA cert then it can’t connect to the old original one. I missed that point! Good you figured it out!!!

Great we got that worked out.

@Sebastian-Roth OK. No problem.

@Daniel-Miller I looked into the speeds, auto-negotiating was set however the speed was messed up. It seems the port on the switch went bad. Plugged into another port and got the correct speed. Imaging seems to be back to normal now.

@Sebastian-Roth Thanks again. I created an new image without that VPN software installed and everything is working as it should. Sorry about this and thanks again for all your help and time.

@george1421 Hey George, sorry for the late reply, work has been closed for Christmas, first day back now.

That has worked, followed those instructions and reran the fog setup and now i can upload images without any issues.

Many thanks,
Pete

@Penguinsec said in Fog Client Not Communicating with Server:

This time client logs are showing no errors, but the host is not showing up in the server.

What do you mean by this??

I will go through the information you sent, but I cannot take photo of the screen. Thanks.

Hello
it’s ok only with: ipxe.pxe, ipxe.kpxe, ipxe.kkpxe, realtek.pxe, realtek.kpxe and realtek.kkpxe.

I will choose ipxe.kpxe because we also have computers on our network with Intel network cards.

Thank you very much and happy new year 2020

@Sebastian-Roth

At some point you might need to think about updating your Ubuntu install but 16.04 LTS is still fine at the moment. No rush.

Yeah thats definately on my to do list!

I don’t think it is something you did. If I remember correctly there was an issue with this link in an older version. As you updated FOG from 1.4.x there is a chance that old version has messed it up. Sorry.

no problem! just wanted to be sure to not repeat it if it were my mistake haha

Learning Linux is a live long task. Even for me, working on Linux every day for many years. Just keep on playing with it and find yourself getting more and more comfortable. A great way is setting up a test environment in a VM where you can snapshot, test and re-install without much trouble…

Yeah, I think I may try and work out of a VM every so often. Tried it before but the timing was unfortunate and I got literally buried at work so I never went back to it but it may be time to give it another go. thanks again for all you’re help! I’ll be back on Monday haha

@Greg-Plamondon Ok, fog-client log looks fine. What about the other things I mentioned?

@mckay You are welcome. This is what the forum is all about! 🙂

Happy new year!

sorry, I didn’t. but I think you can easily recreate this by following your instructions and immediately after the upgrade is finished try to capture a machine.

For bios based computers you would use undionly.kpxe as the default bootloader. For uefi based systems the boot file is ipxe.efi. The next server or boot server value should be the IP address of your fog server.