I am getting DCHP/BootP: Reply not for us. Or PXE- E51 :no dhcp or proxyDHCP offers were recieved
[quote=“Oscar Hilliker, post: 28525, member: 24172”]Fog has been acting odd since 1.0.1[/quote]
Care to elaborate?
Just referring to the issue we had with it in this thread. I was wondering when it is deploying fog says “invalid bios please report” where do we report bios or computer types?
[quote=“Oscar Hilliker, post: 28527, member: 24172”]Tom,
Just referring to the issue we had with it in this thread. I was wondering when it is deploying fog says “invalid bios please report” where do we report bios or computer types?[/quote]
Only when it’s deploying or during the sending inventory part? My guess is the dmidecode that’s trying to read the bios is reporting it can’t find the information. It isn’t something you should report to us, but rather to the software maintainers for dmidecode or report to the motherboard manufacturer if you feel it’s necessary. Most people can just ignore the message though.
Are you still seeing this? We are getting it too. Two identical PCs right next to each other. One will work fine, the other will get the “not for us” message.
Roger, it took us several attempts to get fog to respond. Read Tom’s comment about options 66/67. Keep in mind that like Tom says if you have voip phone’s or anything using TFTP or DHCP server it will sometimes say “response not for us”. I noticed some computers have problems with iPXE, it’s not like the old PXE where you could fog just about anything. Check your TFTP settings on your fog server and sometimes updated the computer’s firmware helps.
UPDATE: we found that if we pull the AC power and the network cable then plug them back in that the PCs image just fine.
[quote=“Roger Saffle, post: 30483, member: 24521”]UPDATE: we found that if we pull the AC power and the network cable then plug them back in that the PCs image just fine.[/quote]
I still can’t believe this worked but it did!!
We were having issues imaging Dell Precision T3500’s. All other computers on the network FOG’ed just fine (with the exception of Dell Optiplex 3020’s but that’s another issue). While researching the 3500’s, I heard my coworker chuckle in the other cubicle. I asked what could make her laugh after fighting with these for days. She mentioned this fix and we went and tried it. Still feeling dumbfounded but the entire classroom is queued up and will be cloning overnight.
I really can’t believe this.
You pulled both power and ethernet?
If you have this issue again could you try just pulling the ethernet cable? There may be a possibility an insertion of a dhcp reset could fix the issue. Maybe?
Note added to Dell [FONT=sans-serif][COLOR=#000000]Precision T3500 and linked it to your post.[/COLOR][/FONT]
I’m guessing that it’s actually a case of the network card not initializing properly. it’s previous state was not being completely cleared on shutdown, but removing power cleared it.
Added to more multicasting troubleshooting.