@arnaudrigole I’m guessing your CIFS/SAMBA shares are mounted as network drives on other computers, yes?
The NFS shares should only be mounted on computers that are going get their image captured or where an image will be deployed and only for the duration of those actions.
I’ve yet to see a virus sniff out possible NFS connections and then be able to somehow use the correct credentials to then infect the shares, but I guess I could be wrong 
@Sebastian-Roth @clemens.g For more details here’s the thread I created on it : https://forums.fogproject.org/topic/6862/can-t-remove-multicast-image-task-through-webgui/7
@Sebastian-Roth It’s likely caused by the autofill feature of certain browsers, would it be possible to add that to the wiki so people are aware that every time they make changes to the storage nodes that they have to enter their actual password?
@arnaudrigole FOG needs NFS access, it won’t use CIFS/SAMBA. I believe there is a tutorial on how to switch over to CIFS/SAMBA but it’s not officially supported.
https://forums.fogproject.org/topic/5145/script-to-install-samba-with-settings-for-fog
@arnaudrigole If NFS is enabled on that server for those directories then yes. If not, you’ll need to set that up.
@arnaudrigole You can’t reexport a directory you’ve mounted with NFS. You need to mount it directly.
@xcvtop On the WebGUI if you click on FOG Configuration it should tell you when you’re no longer up to date (and what version the newest is). Although I’ve found I have to refresh the page after navigating to it before it will tell me so.
@Varion Am I correct in assuming you followed instructions on this page: https://wiki.fogproject.org/wiki/index.php/Installation_on_Debian_Lenny to install fog?
You might want to (temporarily) disable firewall on FOG server to see if that helps.
A note about other Linux distribution
If you are using other Linux distribution such as Debian / Ubuntu / Suse / Slakcware Linux etc., try the following generic procedure. First, save the current firewall rules, type:
iptables-save > /root/firewall.rules
OR
$ sudo iptables-save > /root/firewall.rules
Next, type the following commands (login as the root) as bash prompt:
iptables -F
iptables -X
iptables -t nat -F
iptables -t nat -X
iptables -t mangle -F
iptables -t mangle -X
iptables -P INPUT ACCEPT
iptables -P OUTPUT ACCEPT
iptables -P FORWARD ACCEPT
Mod edited to use code box.
@kortnor What do your host-only network settings look like?
I believe they fixed certain registration issues on trunk 6555+ or so, so it might be worth updating.
@Varion On 1.2.0 I believe ipxe is the standard. Try setting the filename in your DHCP config to undionly.kpxe
Could you share a picture of the boot screen when it fails?
@Tom-Elliott Another thought crosses my mind, does he need a DNS server in his setup?
@mikepel I am aware you can get an IP in windows, but that does not mean you are getting one in PXE environment.
Whatever device you can network boot will do.
Can you do sudo service isc-dhcp-server status -l after attempting to boot your OptiPlex? It will let us know if the DHCP actually attempts to hand out an IP.