I figured it out… turns out, having the addresses of your DNS servers typed in [I]correctly[/I] is important…\

If the issue is specifically on Virtualbox, try ipxe.kpxe or ipxe.pxe.

What kind of switches do you have? Do you have VoIP? Do you have other tftp servers?

On the switches within your environment, do you have Spanning Tree Protocol turned off as recommended? Do you have portfast enabled for cisco switches?

I have finaly found out what went wrong !

I don’t know if there is lot of people using Lancom router but here is the solution :

On Lancom’s router, there is settings for PXE server’s declaration. So no need to set the options 66 & 67.

Just go onto “IPv4” menu then “BOOTP”. Clic on “Boot images…” button and add your FOG server by typing his IP address et boot file (undionly.kpxe). (example on the attached file)

After that, you have to add the station and associate it with your FOG server.
In the same menu as above, clic on “Stations…” and add your computer by typing his MAC address, IP address, station name and PXE server previously declared.

Thank you again for your help and your time 🙂

[url=“/_imported_xf_attachments/0/922_ss_fog02.jpg?:”]ss_fog02.jpg[/url]

I found a work around and tested a few things I found from the forum and iPXE website
It seems seems to be working well on all the computers I have tested so far -
[url]http://fogproject.org/forum/threads/ipxe-issues-work-around.10727/[/url] Just FYI if it helps anyone.

[quote=“Dave Bagwell, post: 29466, member: 5315”]That is what I was trying to say, I removed the domain name from the username and the domain “.com” from the domain name under AD setting.

Thanks again[/quote]

No problem, but you shouldn’t (necessarily) need to remove the .com part of the domain. If the base image is already attached to the domain, changing the domain name field would help.

My guess is your disk was formatted and partitioned using GPT, but the image was in MBR format. These two don’t like playing with each other. I’m sorry, but happy to hear this worked fo ryou.

What FOG Version?

What OS?

Have you tried other kernels?

I had tried 3.14.2 earlier, and it wasn’t working.

I then switched to 3.14.5, and it didn’t work either.

I switched back to 3.14.2, and it started working. (Perhaps only with the “Legacy” switch set to on)

[quote=“Joseph Waldfogel, post: 29366, member: 23569”]Thanks, for the firewall tips, unfortunately none have worked. I have gotten systems to image though. So for now, atleast until I get some of these systems off my plate; I am imaging machines as is. The question I have now is, when I set up Virtual box do I need to change the nat ftp setting to undionly.kpxe. If this needs to be addressed with a new post let me know and I will do so.[/quote]

I don’t NAT in Virtual Box, I run bridged.

Thank you Jamie.
I will keep that in mind. If I go that route, I could use all the help I can get.

Just for anyone who runs into this in the future you can use a clone zilla live usb stick to pxe boot the system to fog.

Takes a flash drive with 140mb of space and works really slick.

I had this issue with our 500B MT’s.

check the /images/dev folder for the temp files named after the mac address of the computer they came from

[quote=“Tom Elliott, post: 29356, member: 7271”]Try the command:
[code]sed -i ‘s/SELINUX=enforcing/SELINUX=disabled/’ /etc/selinux/config[/code]

Normally the /etc/sysconfig/selinux is just a symbolic link to /etc/selinux/config, but sometimes the link doesn’t happen and it becomes it’s own file.

Once you do the sed command, you will likely need to restart the system again.

Thanks[/quote]

Yes, that was it, selinux is now disabled. Thanks for the quick fix.

Thanks for your responses. I’ll be moving this to RHEL6 so this will probably help in case I have any issues. Thanks for all the work on FOG! Been using it for over 4 years and it has been a big help!

Found it, works correctly now. Thanks for all the Help!

🙂 it works for me thank you very much !!!

Time to update 🙂