Welcome to MSFN

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


Can't get TFTP Functioning Properly

5 posts in this topic


I have brandnew box with Windows Server 2008 R2. I'm having issues getting TFTP clients to load from it correctly. DHCP is on the same server with the following options set in the scope:

043 Vendor Specific

060 PXEClient

066 Boot Server Name

067 Boot File Name

DHCP seems to be working fine. I see the PXE Client get an IP, Default Gatway and PXE Boot File name. When it attempts to download the file the following error message appears PXE-E79: NBP is too big to fit in free base memory" So far I have tried three different servers:




All produce the same results. Firewall is off and I have nothing else on the switch except the two machines. The server doesn't have the WDS role installed. I have tried various PXE boot files which I know are working on other deployements.

Anyone have any ideas.



Share this post

Link to post
Share on other sites

What exactly do you have set for option 67?


Share this post

Link to post
Share on other sites


Have NEVER done this (yet...) but I think Tripredacus may be onto something -


You can't load a full-blown Boot Image - it has to have a "loader" (?) that in turn loads the Image.

Found via Google

"PXE-E79: NBP is too big to fit in free base memory" dhcp windows

and appears to work the same way if loading a Linux Image - must use a "loader" to load the Image.


Share this post

Link to post
Share on other sites

Thanks for the reply. I decide to go back to basics and did the following:

- New NIC

- Loaded TFTPD64

- Used its own internal DHCP server

- Had my menu file pointed at my PXE boot image

This time the results were slightly different. I looked like the workstation tried to execute the menu file but then produced the follwing error "mba api not found"

Now, I've been using a PXE builder tool from EMBOOT for about 10 years now. Its version 1.20. I'm wondering if its just too old support execution from a server 2008 and also given its a 64bit o/s. Does anybody know a suitable alternative I could test.

I'm basically just imaging DOS FDD's that contain network boot code.



Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.