And i noticed when client and server are separeted this last DHCP request-ack stage is looped until client get 0x102 and quits.
#Boot camp for mac linux Pc
It turned out to be pretty much the same: First goes DHCP DORA, then some TFTP traffic, then once again DHCP request-ack stage when client PC at the "Contacting WDS server" state. I used tcpdump on a linux gateway and WireShark on the Server to see is there is any difference in traffic between Server and Client PC when it's connected directly and separetly. I knew about ip helpers, but i didn't quite understood how should i use it and, if so, where to implement it, as soon as our switches have nothing to do with DHCP traffic. It sees the server and stuck at "Contacting WDS server" state resulting 0x102 error (AFAIK it stands for timeout or communication error).īut! As soon as i connect this PC directly (using L2 "dumb" switch between Hypervisor and client PC) it boots perfectly.ĭHCP server got it's option "next-server" set to Server's IP. I'm trying to deploy OS into a laptop which is getting it's IP in the same VLAN 10.0.32.X/24 via UEFI PXEv4 boot. VM is getting DHCP address 10.0.32.100 which is bound for it's MAC.
VM with Server 2019 (also tried 2022) with WDS role and MDT installed, connected to one of the switches.Allied Telesis switches as access switches.
0 kommentar(er)
