@george1421
i dont know how much more time i will invest in this.
I maybe just try to build a mini-network to be able to use fog.
I really dont care too much if its all automatic. I also saw the article on how to change the bios/uefi file for machines.
As i saw so far i only have to use uefi-machines, so it wouldn’t matter.
As it came out today, option 11 isnt needed anymore. I used the ip for option 66 and ipxe.efi for 67.
I installed wireshark on the notebook and made a test with ipconfig /release and /renew.
The notebook received the correct ip, filename and destination server with the dhcp offer.
When i bootet it again, it did not care again and just downloaded the citrix nbp-file.
Is there some sort of cache involved on the dhcp-server or client that i maybe have to flush/configure?
The citrix-environment is really the main focus in our company. We have well over 100 clients using this daily and i’m not the caretaker for this service. So my goal is to get it working with changing as little as possible on the citrix service.
I opened up all ports on the fog server, to make sure nothing is blocked, but i was again only seeing dhcp requests and discoveries. Not to my surprise because the client does, as mentioned above, never try to boot from there.
Something special about that was, that for each dhcp-request on port 67/68 (dont know exactly anymore) a ‘destination unreachable port unreachable’ answer was generated. i dont know why or where this should come from, as i have opened all input traffic.
Im not at work right now and i’ll see if i get the time to provide something too look at. Maybe i just have time in the evening (like now) to add some more detail.
Another question: We have a kind of test-environment based on a seperate vlan.
Does a vlan matter if all traffic is handled on the same one? generally is a vlan a problem?
I can ping the fog-server from the notebook / other clients, so the connectivity is there.