@DJ Amazing we found this after such a long time of intense digging in packet dumps and testing. Thanks for posting the information on the switch so people can find this here in the forums.

I have though about this but don’t really see why we should “fix” NFS mount to use high source ports. I might be wrong here but from what I have seen in the packet dumps it seems like this is general behavior and changing this would need a fixup deep down in the NFS client libs code - something that we would need to maintain over a long time since I don’t see this change making it into the official code line. What do you think?

@dj FOS (name for the FOG system that loads at that point) doesn’t need /sbin/mount.nfs

I just checked and tested and it all works fine in my environment.

Can you run mount -v | grep images on a system where you were able to mount the nfs share and take a screenshot/paste it here?

What Ubuntu version is the FOG server running btw?

Did you test the mount in FOS on a system that mount does work in a full linux distro?

We now have the client PC booting and downloading the undionly.kpxe file but had to use the above mentioned “class” option. Further investigating the “Connection timed out” issue has raised another set of problems/questions which I will followup in a new thread.

Or try the new compiled “HostNameChanger.dll” from jbod (Thread: [url]http://fogproject.org/forum/threads/fog-1-2-0-product-key-changer.12510/#post-42958[/url])
Replace the file on the client(s) -> restart Fog Service.

[url]https://dl.dropboxusercontent.com/u/18664328/HostNameChanger.dll[/url]