This did work for the 760’s and 780’s as well. Thank you very much for the help Jbob, Junkhacker, and Tom
Posts made by mbeeler
-
RE: FOG 1.2.0 w/ DHCP/BOOTP Reply not for us
-
RE: FOG 1.2.0 w/ DHCP/BOOTP Reply not for us
Jbob thank you that seems to be working on the 755, I will be able to test on the 760 and the 780 later this afternoon.
-
RE: FOG 1.2.0 w/ DHCP/BOOTP Reply not for us
So what has changed from version .32 where this worked with no problems on our network to now? We do not have STP enabled on our network. All switches are Extreme Networks brand
-
RE: FOG 1.2.0 w/ DHCP/BOOTP Reply not for us
I can now add a third model to my list that will not work. So total that I have on my campus that will not register with fog include Dell optiplex 755, 760, and 780. They all three give the DHCP/BOOTP Reply not for us error.
-
RE: FOG 1.2.0 w/ DHCP/BOOTP Reply not for us
After letting them sit for awhile they do go into the registration process then do what is in the picture.[ATTACH=full]1264[/ATTACH]
[url=“/_imported_xf_attachments/1/1264_2014-08-07_11-09-35_290.jpg?:”]2014-08-07_11-09-35_290.jpg[/url]
-
RE: FOG 1.2.0 w/ DHCP/BOOTP Reply not for us
I have tried both undionly.kpxe and undionly.kkpxe from official 3.14.2 kernel as well as the unofficial 3.16.0 kernel. They both still give me the DHCP/BOOTP Reply not for us message on the Optiplex 755 have not tried on the 760 yet.
-
RE: Pxe not working after update
In Ubuntu 12.04 and later the tftp starts to soon after a reboot. I have had good success with doing the following.
sudo gedit /etc/rc.local
then add the following line
/bin/sleep 30 && /etc/init.d/tftpd-hpa restart -
RE: FOG 1.2.0 w/ DHCP/BOOTP Reply not for us
I have a lab of 1600’s that is currently being deployed. Once it is done I will try that one and let you know. Is there a process I need to do to undo the chainloading of pxe to ipxe or will it matter?
-
RE: FOG 1.2.0 w/ DHCP/BOOTP Reply not for us
I am not sure on portfast, STP is disabled but there is plans to enable extremes version of STP called ELRP.
-
RE: Images in Database
There is a tftp password setting under other settings>>fog settings as well, toward the bottom of the list.
-
RE: FOG 1.2.0 w/ DHCP/BOOTP Reply not for us
Windows server is a 2008 R2 and all switches are extreme networks. Fog server is an optiplex 745.
-
RE: FOG 1.2.0 w/ DHCP/BOOTP Reply not for us
When attempting undionly.kpxe we could not get any of them to work. After following the guide to chainloading PXE to iPXE we were able to get at least the 745’s and 1600’s to work.
-
RE: Images in Database
Within the webgui is where I changed mine. I do not recall changing it anywhere else.
-
RE: Database Schema Installer / Updater keeps starting up everytime FOG is restarted
No, problem. I hope it works for you.
-
RE: Images in Database
You may want to verify the correct password is in place under the storage management link. I am thinking that is where i finally fixed my issue that was similar to yours
-
RE: Database Schema Installer / Updater keeps starting up everytime FOG is restarted
In the more recent versions of ubuntu tftp starts before it grabs the IP address. If i remember correctly you can fix the tftp issue by editing /etc/rc.local file. Add in “/bin/sleep 30 && /etc/init.d/tftpd-hpa restart” with out quotes. This should restart tftp for you after a reboot.
-
RE: Database Schema Installer / Updater keeps starting up everytime FOG is restarted
run from terminal “sudo service tftpd-hpa restart” and try again
-
FOG 1.2.0 w/ DHCP/BOOTP Reply not for us
Current OS: Ubuntu 14.04
Current Fog: 1.2.0
Current Kernel: Unofficial Published Kernel 3.16.0 x86_64
Windows DHCP server with 067 set to pxelinux.0 and 066 set to ip of fog server
Followed [URL=‘http://fogproject.org/wiki/index.php/Chainloading_PXE_to_iPXE_using_pxelinux.0’]guide[/URL] to chainloading PXE to iPXE because we could not get undionly.kpxe to work.Dell optiplex 755 gives a No DHCP or proxyDHCP offers were received. If allowed to boot to windows then restarted it will get past that and then give us a DHCP/BOOTP Reply not for us.
Optiplex 760’s also give the Reply not for us error but do receive a DHCP address with out going to windows first.
So far it seems to work just fine on our optiplex 745’s and Precision T1600’s.