@tombagley ignoring a mac in fogs webif just ignores it for the specific host not the whole system!

@waynejitehead i simply remove the usb nics mac after deployment because it does not belong to the system, this way new hosts with same usb nics mac will propperl recognized. Regards X23

@george1421 sorry, i was still researching what might be happening. For a little bit more background, i can’t get my vm to boot to the win10 1803 iso using efi but I didnt have an issue with the ltsb version last year. I setup a second esxi server for testing, running 6.5 to see if it was issue with 5.5 and i am able to boot win10 1803 using efi on that test server but not able to pxe boot. efi network comes up then says downloading nbp file then continues booting. I dont see any other messages but i will do a slow mo video see if i can see if anything flashes up briefly. On the production server that I can’t get the iso to boot, I was able to get it to pxe boot after i deleted the nic and re-added it using vmxnet3. recap: prod esxi server 5.5u3 – cant boot 1803 iso using EFI Test server esxi 6.5, able to boot iso to EFI but cant PXE boot EFI. I just did quick google search that brought me to this thread and was just making a general commenting that i was having issues. i can make a new thread if that would be better.

@bmacadre Try to put the FOG Server on one of the 100Mbps ports. This would obviously severely hinder unicast imaging, but if you’re mostly doing multicast then this might work better.

@george1421 Fog has been working, but I haven’t had any machines to test a multicast on since we last spoke. I am going to attempt to image a classroom today and will report back.

@george1421 I replicated my images using rsync and verified that all images are in both locations. I also have a backup of my images off of both of the nodes. I went in and I created a new Storage Group. I associated the Storage Node that is not the Master Server with the new Storage Group. I then associated a number of my images with that Storage Group. My goal is to have some images only reside on the node in the new Storage Group and some only reside on the other Storage Group. I set both servers to be the Master Node for their Storage Group. Based on the warning I read about setting a server to the Master Node I half-way expected for any images that were not associated with that Storage Group to be purged from the Master Node but that didn’t seem to happen, which is fine. Is it now safe to go back and purge images from servers via cli if they reside in an image store on a node that is not in the Storage Group that is associated with that image? Thank you!

@dseecharran22 said in Fog on a Isolated Network: when I move over and plug the server into the switch and reload the web interface, it says it cannot communicate with that server. Dumb questions but they need asked, please answer each one. When you move the server to that other switch, are you moving your workstation/laptop to that other switch too? So that it can talk to the server? Can you successfully ping the FOG Server from your workstation once on the isolated network? Can you successfully SSH into the FOG Server from your workstation once on the isolated network? Status of the apache service on your server. debian/ubuntu would be systemctl status apache2 -l and centos/rhel/fedora would be systemctl status httpd -l On the server via CLI, what is the output of this command: curl http://localhost/fog/managemement and curl http://127.0.0.1/fog/managemement

@nt_tech I would recommend Debian 9. I have a number of reasons for this.

@wayne-workman that was basically it. worked extraordinarily well with the one. my initial setup and testing, i didn’t have control over the dhcp server so i had to do it with two. it worked at that site, but there were flaws. once deploying it, a mix of hardware issues, network issues, and ultimately permissions on things caused problems. thanks for all you guys do though.

We have ended up rebuilding our image and it is now working OK. It mustn’t have liked something in our old image. Thanks for your help and suggestions!

We have made a special setting in deploy.image menu for the computers of the room. Then login and password are not requested to access to deploy menu. #login params param mac0 ${net0/mac} param arch ${arch} param hostname ${hostname} goto host_${hostname} || goto autres :host_bug :host_win10-3 :host_i207m01 :host_i207m02 :host_i207m03 :host_i207m04 :host_i207m05 :host_i207m06 :host_i207m07 :host_i207m08 :host_i207m09 :host_i207m10 set username userlogin set password userpassword params param username userlogin param password userpassword param qihost 1 isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme goto fin :autres login params param username ${username} param password ${password} param qihost 1 isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme :fin

@george1421 Ok, sorry about not getting back to this sooner, but work has been a bit busy. So anyway, I made the changes to the config file. (basically I created the ltsp.conf because it did not exist in the dnsmasq.d directory) there was only a README file. I was able to do a TCP dump and cap the information. But I have a feeling it will not be much help, I did see that I am running 2.75 version of dnsmasq, but I can reload the VM to just before I installed DNSMASQ and make sure the 2.76 version is installed. *will update if there are any changes from that versioning. Thanks for the help!

@tlyneyor said in Connection time out (4c0a6035): However unfortunately I am running through the imagine process and it is painfully slow. To the point where selecting the image and the group etc needed 3 or 4 attempts each, and it is currently downloading the image at around 50MB/min. It screams network issue to me, but there are no other network problems at all that I can see, and I have run another machine in the same switch with no latency or connectivity problems. That sounds like it could be a duplicate IP. You’ll get a ton of slowness and intermittent transmissions with a duplicate IP.

@srd said in Chain loading error: @brendojohnso Did this ever get resolved? I am having the same problem. Please open a new thread because your conditions may be different than this OPs. Please include what version of FOG you are using, what linux distro that powers your FOG server and a clear picture of the error you are seeing.

Wooooooow it looks great! I’ll poke around and hunt for some bugs. :)