@tgidwani Wow. Really glad you figured that out. I have done a lot of networking but I wouldn’t have expected the gateway setting to cause such an error. In theory the gateway information is only ever used when the host tries to connect to a machine that is not within it’s own subnet. So gateway shouldn’t play a role here as long as both were in the same subnet.

Are you able to replicate the issue when putting the GATEWAY= line back into the config??

@michaeloberg Did you ever solve this?

@VijayBomble Any news on this?

@DeRo93 said in Database connection unavailable - Login incorrect on FTP and Ubuntu:

But maybe you can tell me if this happened because the Ubuntu Server did an Upgrade or something?

Probably yes. But you may check the update log in /var/log/apt/history.log…

@Landy_Dan The FOG CA was introduced to secure the connection between fog-client software and the FOG server. We use certificate based state of the art encryption for that. But you need to know that it is a self signed CA and not derived from an official authority.

Not sure if it’s wise (and even possible) to use that for your RADIUS project. Give it a try and see how far you get. Start by taking a look at all the certificate stuff in /opt/fog/snapins/ssl/ on your FOG server.

Make sure your firmware is up to date in this hardware. Its failing between the UEFI PXE rom hand off and iPXE starting. Typically when we’ve seen this in the past it was related to cruddy early generation firmware.

Weird, disregard. It just suddenly started working now. No idea what fixed it. Maybe it took a while for something to register.

@Sebastian-Roth

I did not found the option in FOG configuration -> fog settings , but I just found the faulty host had as primary MAC the Windows vNIC mac. I put the MAC of the physical NIC as primary and then everything back to normal.

I don’t have a idea to make the research better as I just had to search in the host section of FOG the MAC addresses found in the client log to see what was going on.

Thanks Fernando
I was able to download FOG using the link you provided

I don’t know what happened but now it’s just capturing used space.

Captura de tela de 2019-05-17 10-01-04.png Captura de tela de 2019-05-17 10-42-28.png

Thanks for that link. I’ll peruse it as well. At least Fog is old faithful and got my test computer up and running when USB/DVD both failed me miserably!

@george1421 That makes sense . Thanks very much sir!

https://forums.fogproject.org/topic/10944/using-fog-to-pxe-boot-into-your-favorite-installer-images

Windows is a unique critter, but its possible if you create a winpe environment and then start the windows installer from a windows network share.

It seems like you have an nvme raid0, some linux based imaging solutions have problems with that.
As you say you must change from raid to sata to capture/deploy, clonezilla partclone make that suggestion.

I can see the pc that you link, so i cant help you with bios.

The computer must have an option to change it. Search a few more.

@Fernando-Gietz
Thanks.
You can set status to solved

@Sebastian-Roth Yeah, it was honestly my fault. Normally I’d capture and deploy immediately after to test, but these past few weeks have been ridiculously insane for me and my machine to image allocations haven’t been as up to date as they normally would’ve been.

I noticed this happened once before with a Windows image, but it was related to the dirty bit and another issue I found here. All in all I wanted to at least report and give this a go, I apologize for taking your time but as always appreciate the help. If this does happen again, I’ll be sure to give those kernels a go and report back here the results.

Configure the snapin to be replicated on the locations nodes, configure FOG to get the snapin from the location, be sure to be configured in general, as default and on the client settings.

Be sure that the snapin is replicated on the server you need and try it.

maybe you need to change, on the Snapin Pack Arguments the &quot ; by "

@Sebastian-Roth It works! Thank you for your help.

Starting deploying and image and ended up not having enough hard disk space (oops) but its all working correctly now. Learnt quite a bit from this experience as well. Thanks again

@Junkhacker

Thank you for the assistance. This issue was resolved. I’m not sure how to mark this as resolved though.