KACE Product Support Question
KACE K2000 PXE Boot TFTP Timeout Across Subnets
Since moving our clients onto a different subnet, we can no longer PXE boot to the K2000.
The K2000 is on 192.168.0.13 and the clients have moved to 192.168.2.0/24.
I have moved the DHCP options 66, 67 and 244 from the 192.168.0.0 DHCP scope to the new 192.168.2.0 DHCP scope.
The client is able to find DHCP and get an IP address from the new DHCP scope, but then shows a TFTP open timeout.
I can ping the K2000 from any client.
If I download the boot environment and create a bootable USB I can boot a client onto the K2000.
Everything else is working fine, there are no restrictions between subnets, no firewalls in the way.
If I try to manually get the boot image from a client with "tftp 192.168.0.13 get kbe0028.iso" I get "Connect request failed". This would seem to be the key issue but I don't know why this doesn't work.
I've been over a number of threads on this issue but have not found a solution so far.
Any help would be greatly appreciated.
Community Chosen Answer
By default this is not possible.
Best practices is still: keep the appliance in the same subnet like the clients.
The option with the remote site appliance (RSA) in the target subnet is also always a good option.