PXE Boot on different VLAN
Hello,
I am having problems of not being able to boot using IPv4 PXE when I'm trying to load the operating system image onto a laptop from my MDT/WDS server. It is however getting an IP address from the DHCP server, particularly when the laptop is on a different VLAN. Let me explain in better detail...
I have setup, using MDT, an operating system image which I wanted to deploy over the network for clients to image. The WDS is the type of application that I use put the boot image file onto PXE. This server is on VLAN10, along with a Windows DHCP server which is also connected on the same VLAN. The DHCP server is configured to manage the domain network VLANs, for instance VLAN10 & VLAN20. So when I connect the client machine onto VLAN10 which is the same network as the servers, the PXE boot works perfectly fine and loads the image. I would like to be able to have my client machine to be connected onto VLAN20 but to get the boot image through via VLAN10 - This is the bit that I am struggling with at the moment.
I have been doing a quite a bit of extensive research and have configured the DHCP Options on the DHCP server to only VLAN20 Scope (it boots with IP but waiting for TFTP server), but being told by Microsoft that these aren't supportable? I have noticed that many say that I should configure "IP Helper" on my network environment, but I don't know how I would do this with my TP-LINK switches (TL-SG2016P & TL-SG2428P), esepcially when we have a Omada Cloud Controller in place, which can make this situation a bit tricky.
So I am struggling at the moment and any help or suggestions would be greatly aappreicated.
Many thanks,
Ben