Our KACE2000 ( is working great on it's local subnet, but we are having issues deploying systems in a branch office. This is what we have done:

The firewall in our main office ( is allowing all ip traffic in both directions between the sites.

The router ( in the branch office ( are also the DCHP server for that location with the following configured options:

dns-server (dns server in main office)
option 66 ip
option 67 ascii kbox2000.0

However, as we PXE boot the clients and get IP etc, the following errors are ruining the fun.

PXE-E32: TFTP open timeout

PXE-M0f: Exiting Intel Boot Agent.


I've tried troubleshooting TFTP by using Telnet, but that doesn't even seem to "work" on the local subnet.


Any ideas?

Answer Summary:
1 Comment   [ - ] Hide Comment


  • Solved by workaround, read below
Please log in to comment

Answer Chosen by the Author


first I'd make sure the firewall is allowing UDP and TCP traffic as typically tftp uses UDP protocol

then I'd get on a machine on the subnet in question and see if I could pull data from the K2000 with the tftp client.

Windows machines  the tftp client needs to be turned on
 Linux machines may need to have it installed depending on the distribution

Assuming windows, open a command prompt   (turn off the windows firewall as it will block even outgoing tftp requests )
type :   tftp K2IP get netbootintel/i386/booter

Now you will either get a connection fail  or the command will complete and you will see a 500k file called booter in the directory you ran the command from.

if the connection fails,  run the same test on the subnet you CAN PXE boot from  (as a control) it should work there.
then investigate why the request is failing to cross your subnet.

While you are running this test, you should also test mount the K2000 samba shares to make sure there are no issues there as well.
Answered 08/14/2014 by: genfoch01
Orange Senior Belt

  • TFTP didn't work out for me, it returned the following. This was tried from the local subnet where PXE is working and no firewall exist.

    c:\>tftp get netbootintel/i386/booter
    Error on server : File not found
    Connect request failed

    The Samba share is accessible from both sites.
    • well that looks like you did make a connection
      the response you got "file not found" is coming from the tftp server

      I gave the path for an OSX boot I am sorry about the confusion. go into your deployments > boot environments and open the detail page on any of your working KBE's. the URL at the top will have "boot_image_id=XX"

      as an example here is the url for the detail page of my default x64 kbe

      so I will use 24 in place of XX in my examples :

      change the command to tftp K2IP get kbe00XX.iso
      it will take a little longer because its a 200 - 300 mb file

      example of a good response :
      tftp get kbe0024.iso
      transfer successful : 258046340 bytes in 91 seconds

      example of a connection with a bad file name
      tftp get badfilenamehere
      Error on server : File not found
      Connect request failed

      example if the tftp server can not be reached at all
      tftp get kbe0024.iso
      timeout occurred
      connect request failed.

      so it looks like you did make a connection to the tftp server on the k2000 from its subnet.
      try it from your "bad" subnet
      • Ah ok, of course.

        Yes, it works fine from both subnets,
        C:\>tftp get kbe0035.iso
        Transfer successful: 192132329 bytes in 180 second(s), 1067401 bytes/s

        Best Regards,
      • So what can it possibly be? Something with the DHCP option 66 and 67 that isn't working as they should?
      • I would create a USB boot key (admin guide page 94 for K2 version 3.6 ) and see if you can boot the machine on the bad subnet with it. If you can, then go into "recovery" and open a command prompt and then run kgetdhcp 66 (which should return the IP of your K2000 ) and kgetdhcp 67 (which should return k2000.0 )
      • I've created a USB boot key, that works fine on the main subnet. When I try to boot a machine on the bad subnet I get these errors.
      • From your screenshots it looks like DHCP option 66 is not setup/working correctly. It should be returning the IP of your K2000 and as you can see it is not. I'd start there.

        as another test, you could use KBE Manipulator
        to build a KBE with a hard coded IP for the K2000 (bypassing the kgetdhcp ). you would still have to load it to a usb key but if that works on your "bad" subnet the issue would for sure be limited to the DHCP option 66 setting.
      • Yes, after hard coding the KBOX IP with KBE Manipulator, I can successfully boot all the way into the menu. This is good enough, thank you!
Please log in to comment
Answer this question or Comment on this question for clarity



Not a network guy but we had a similar situation our network guy resolved by entering a few commands into the switches/routers.(17 remote locations)

We were implementing Wake-on-Lan and ran in to the same limitation. I think he resolved it with an IP Helper Address.

May or may not work for you but here is a link that I think goes over the process. Good Luck.


Answered 08/14/2014 by: danwilsn
White Belt

  • Thanks. Not a network guy either, but I'm pretty sure that IP Helper is used during the DHCP discovery process, to help the PXE clients reach a DHCP server located on another subnet. In our case the remote router is supplying the remote PXE clients with IP's and that part seems to work out well.
Please log in to comment
This content is currently hidden from public view.
Reason: Removed by member request
For more information, visit our FAQ's.