Topics created by anwoke8204

@dellborg82 What was the issue? This way somebody else who may be having a similar issue can also be helped?

@Tom-Elliott no, on the client we are getting the permission denied. so we are going to replace the hard drive and then try again.

@DBCountMan If I recall correctly, this is on purpose. It’s been a while since I looked at it, but we set LDAP users to a specific set of identifiers and filter those out of the view because things you can do with local users (change password, etc…) you should not be able to do with LDAP based users.

@anwoke8204 If your computer is uefi based, lets try the easy method first. https://forums.fogproject.org/topic/6350/usb-boot-uefi-client-into-fog-menu-easy-way

By using the easy method above, you can retain all of the features of the FOG preboot environment. If that method doesn’t work we can build FOS Linux on a usb flash drive and boot that way. Its a little more complicated to setup but I have an image already created you can use. https://forums.fogproject.org/topic/7727/building-usb-booting-fos-image the previous link is the instructions to build it yourself. Make sure you read through the caveats if you go this route.

@anwoke8204 In this article https://www.cherryservers.com/blog/how-to-configure-ubuntu-firewall-with-ufw There is a section about logging. It kind of indicates that the default deny policy logs blocked packets in /var/log/ufw* files. Lets see if there is something there regarding to what nfsv3 is trying to do. I don’t have ufw enabled on my fog servers so I have not run into this issue before.

It looks like you have all of the rules/ports enabled.

@anwoke8204 said in Fog taking forever to boot to the network:

tftp 10.4.47.15 ipxe.efi c:\users\kstevens

Hopefully you just missed the action command when you posted the command.

The command should be
tftp 10.4.47.15 get ipxe.efi c:\users\kstevens and it should place the file ipxe.efi in the directory path you provided. It concerns me that the destination file name did not match the source name. The transfer should be very quick like about 2-3 seconds from the time you hit enter on that get command.

What are ping times to this fog server 10.4.47.15 from this same windows test computer?

What are ping time if you use this command ping -4 -l 1300 -n 4 10.4.47.15 This command says use ipv4 set the payload size to 1300 and ping 4 times to the host. I’m specifically using a payload size larger that the default ping size to see if we are hitting a mtu issue that wouldn’t be visible with a 64 byte ping size.

@anwoke8204 Start by looking at the log file in C:\fog.log to see if the fog-client software is properly working.

@anwoke8204 said:

it attempts to pass off to the hard drive, but it doesn’t, just goes back to the fog menu

I am wondering on what happens if you switch from PXE boot back to just plain boot from disk? Does it boot Windows 10 properly then?

I have tried both bios and uefi. and I get the same issue.

What exactly to you mean by that? Did you play with the exit type settings for both in the web UI or did you switch the BIOS/UEFI firmware settings on the host? If you played with the firmware settings on the host I am really wondering if your image is UEFI or legacy BIOS? You can’t have a pure UEFI image and boot that on a legacy BIOS only machine or vice versa.

Which exit type is set in the web UI? Have you tried all the different ones like SANBOOT and so on?

Be aware there is a global setting for exit type as well as a per host setting.

ok I got past that issue by following the following form Thread [url]http://fogproject.org/forum/threads/problems-when-installing-on-rhel-6-3.4017/#post-10653[/url]

but now I am getting the following error
Setting up and starting VSFTP Server…Failed!

at first I thought it was because I had the ClearOS FTP app installed which I believe uses proftpd, so I uninstalled it, but I still get the same error. is there an install log I can check or something to find out why?