@Junkhacker, it worked! Thanks!

Problem solved.It was an old image…

Could this be an IO error beyond 2 GB ?
That used to happen on older 32-bits systems, and is still something to care about with minGW.
I would not expect that from Ubuntu x64, but that conclusion may depend on the compiler used.

Did you check the rcs? I’m pretty sure this was addressed already.

Please install the latest rcs of which you’ll find this issue is already fixed.

@jpaul said in network printers not coming in when imaging with fog 1.2.0:

ill not populate even after all the forced group policy updates per machine . Has anyone found the the problem might be with fog imagining or is it just something wrong with our group policies,

@jpaul it sounds like an issue with your GPO. Is there also a reason why you just started using 1.2.0? It’s fairly outdated and doesn’t support newer operating systems (like Windows 10) very well.

@Tom-Elliott Its works! I’m with RC12 version with dev-branch. Thank you very much for your help.

Running Version 1.4.0-RC-12 SVN Revision: 6069

@Tom-Elliott @ftgjason Sorry missed notifying.

Tom You are the best.

I installed 1.3.5 and it is now working.

Thanks!!!

@Tom-Elliott Thanks Tom, I had the same problem and this fixed it for me!

I have solved my problem. The first problem (connection timeout) comes of the switch, I have change for a router and it works ! The second problem, I have reinstall Windows 10 and it works, I can capture my physical machine !

Thank you for all your help !

@george1421 we moved the conversation to IM since turn around time was much quicker.

We got dnsmasq setup with all of the configuration required to pxe boot in a home router environment. DNSMasq probably won’t be needed in a business envionment since a business will typically have a dedicated dhcp server where you can set dhcp options 66 {next-server] and 67 {boot-file}. In the case of the home routers, dnsmasq will provide these missing values.

At this time the OP is able to pxe boot the VM target computer and was in the process of registering the VM with FOG.

Marking topic solved.

@Tom-Elliott there were few corrupted files on windows and fixed them, and after those it worked fine

That solved it @Tom-Elliott thank you very much. Life saver!

@Tom-Elliott I see. Ya it should have at least told me what interface after the “from”, didn’t realize that until now. Thanks Tom!

@Tom-Elliott will try a reboot. If you think another boot file would be better, please let me know.
Thanks man. You are extremely helpful. Have a great day!

@juanflis Please check your /images/ permissions.

Please make sure they’re sudo chmod -R 777 /images and sudo chown -R fog:root /images

@EspenU yes.

@Psycholiquid I don’t mind, I use VMWare myself 🙂

Yes, that portion seems to be working now. On to the next bug…