Configure PXE Server In Ubuntu 14.04

PXE (Preboot Execution Environment) Server allows the user to boot a Linux distribution from a network and install it on hundreds of PCs at a time without any Linux iso images. If your client’s computers don’t have CD/DVD or USB drives, or if you want to set up multiple computers at the same time in a large enterprise, then PXE server can be used to save money and time.

In this article we will show you how you can configure a PXE server in Ubuntu 14.04.

To get started, you need to first set up your PXE server to use a static IP. To set up a static IP address in your system, you need to edit the “/etc/network/interfaces” file.

1. Open the “/etc/network/interfaces” file.

Add/edit as described below:

Save the file and exit. This will set its IP address to “192.168.1.20”. Restart the network service.

DHCP, TFTP and NFS are essential components for configuring a PXE server. First you need to update your system and install all necessary packages.

For this, run the following commands:

DHCP stands for Dynamic Host Configuration Protocol, and it is used mainly for dynamically distributing network configuration parameters such as IP addresses for interfaces and services. A DHCP server in PXE environment allow clients to request and receive an IP address automatically to gain access to the network servers.

1. Edit the “/etc/default/dhcp3-server” file.

Add/edit as described below:

Save (Ctrl + o) and exit (Ctrl + x) the file.

2. Edit the “/etc/dhcp3/dhcpd.conf” file:

Add/edit as described below:

Save the file and exit.

3. Start the DHCP service.

TFTP is a file-transfer protocol which is similar to FTP. It is used where user authentication and directory visibility are not required. The TFTP server is always listening for PXE clients on the network. When it detects any network PXE client asking for PXE services, then it provides a network package that contains the boot menu.

1. To configure TFTP, edit the “/etc/inetd.conf” file.

Add/edit as described below:

Save and exit the file.

2. Edit the “/etc/default/tftpd-hpa” file.

Add/edit as described below:

Save and exit the file.

3. Enable boot service for inetd to automatically start after every system reboot and start tftpd service.

4. Check status.

It will show the following output:

Now you need the PXE boot file “pxelinux.0” to be present in the TFTP root directory. Make a directory structure for TFTP, and copy all the bootloader files provided by syslinux from the “/usr/lib/syslinux/” to the “/var/lib/tftpboot/” path by issuing the following commands:

Set up PXELINUX configuration file

The PXE configuration file defines the boot menu displayed to the PXE client when it boots up and contacts the TFTP server. By default, when a PXE client boots up, it will use its own MAC address to specify which configuration file to read, so we need to create that default file that contains the list of kernels which are available to boot.

Edit the PXE Server configuration file with valid installation options.

To edit “/var/lib/tftpboot/pxelinux.cfg/default,”

Add/edit as described below:

Save and exit the file.

Edit the “/var/lib/tftpboot/pxelinux.cfg/pxe.conf” file.

Add/edit as described below:

Save and exit the file.

For this, Ubuntu kernel and initrd files are required. To get those files, you need the Ubuntu 14.04 Desktop ISO Image. You can download the Ubuntu 14.04 ISO image in the /mnt folder by issuing the following command:

Note: the download URL might change as the ISO image is updated. Check out this website for the latest download link if the above URL is not working.

Mount the ISO file, and copy all the files to the TFTP folder by issuing the following commands:

Now you need to setup Installation Source Mirrors via NFS protocol. You can also use http and ftp for Installation Source Mirrors. Here I have used NFS to export ISO contents.

To configure the NFS server, you need to edit the “/etc/exports” file.

Add/edit as described below:

Save and exit the file. For the changes to take effect, export and start NFS service.

Now your PXE Server is ready.

A PXE client can be any computer system with a PXE network boot enable option. Now your clients can boot and install Ubuntu 14.04 Desktop by enabling “Boot From Network” options from their systems BIOS.

You’re now ready to go – start your PXE Client Machine with the network boot enable option, and you should now see a sub-menu showing for your Ubuntu 14.04 Desktop that we created.

pxe

Configuring network boot installation using PXE server is efficient and a time-saving method. You can install hundreds of client at a time in your local network. All you need is a PXE server and PXE enabled clients. Try it out, and let us know if this works for you.

Reference: PXE Server wiki PXE Server Ubuntu

Image credit: fupsol_unl_20

59 comments

  1. Great article, thank you for writing it.

    Here’s what I encountered:

    -I was using a different DHCP server on the network, so didn’t touch that part of the guide. I also used a different IP address.

    -Needed to change “vmlinuz” to “vmlinuz.efi” when copying and in the PXE menu config (I was using Ubuntu 14.04.3 as well).

    -I copy/pasted the contents of pxelinux.cfg/default, and had to edit the IP address of my server. My copy/paste also wrapped lines right before the initrd= and it became a new line. This ended up producing an error on booting the client machine: “Kernel panic – not syncing: VFS: Unable to mount root fs on unknown-block”

    • make sure in /var/lib/tftpboot/pxelinux.cfg/default file

      this is a single line not two lines

      “append boot=casper automatic-ubiquity netboot=nfs nfsroot=192.168.1.20:/var/lib/tftpboot/Ubuntu/14.04/amd64 initrd=Ubuntu/initrd.lz quiet splash”

      Also can you give me the output of /var/log/syslog file and /var/lib/tftpboot/pxelinux.cfg/default file ?

      And other questions is, which DHCP server you have used like Microsoft windows or router ?

  2. Hi,

    Nice guide..!!!

    I facing issue on client side while booting through network ubuntu 14.10, i.e Bad archive mirror.

    I checked all the configuration correct.

    Kindly suggest.

    • Which Operating system you are trying to boot from PXE server Ubuntu-14-10 server or Ubuntu14-10 Desktop.?

      Also, give me the output of /var/log/syslog file and /var/lib/tftpboot/pxelinux.cfg/default file.

      • Ubuntu-14-10 Desktop..

        sysylog:

        # D-I config version 2.0
        # search path for the c32 support libraries (libcom32, libutil etc.)
        path ubuntu-installer/amd64/boot-screens/
        include ubuntu-installer/amd64/boot-screens/menu.cfg
        #default ubuntu-installer/amd64/boot-screens/vesamenu.c32
        default tftpboot/vesamenu.c32

        prompt 0
        timeout 0

        DEFAULT vesamenu.c32
        #UI vesamenu.c32
        TIMEOUT 100
        PROMPT 0
        MENU INCLUDE pxelinux.cfg/PXE.conf
        NOESCAPE 1
        LABEL Try Ubuntu 14.04 Desktop
        MENU LABEL Try Ubuntu 14.04 Desktop
        kernel Ubuntu/vmlinuz
        append boot=casper netboot=nfs nfsroot=192.168.1.64:/var/lib/tftpboot/ubuntu-installer/amd64/
        #initrd=Ubuntu/initrd.lz quiet splash
        initrd=ubuntu-installer/amd64/initrd.gz quiet splash
        ENDTEXT
        #LABEL Install Ubuntu 14.04 Desktop
        #MENU LABEL Install Ubuntu 14.04 Desktop
        #kernel Ubuntu/vmlinuz
        #append boot=casper automatic-ubiquity netboot=nfs nfsroot=192.164.1.64:/var/lib/tftpboot/ubuntu-installer/amd64/
        #initrd=Ubuntu/initrd.lz quiet splash
        #ENDTEXT

        ===========================================================

        default:

        # D-I config version 2.0
        # search path for the c32 support libraries (libcom32, libutil etc.)
        path ubuntu-installer/amd64/boot-screens/
        include ubuntu-installer/amd64/boot-screens/menu.cfg
        #default ubuntu-installer/amd64/boot-screens/vesamenu.c32
        default tftpboot/vesamenu.c32

        prompt 0
        timeout 0

        DEFAULT vesamenu.c32
        #UI vesamenu.c32
        TIMEOUT 100
        PROMPT 0
        MENU INCLUDE pxelinux.cfg/PXE.conf
        NOESCAPE 1
        LABEL Try Ubuntu 14.04 Desktop
        MENU LABEL Try Ubuntu 14.04 Desktop
        kernel Ubuntu/vmlinuz
        append boot=casper netboot=nfs nfsroot=192.168.1.64:/var/lib/tftpboot/ubuntu-installer/amd64/
        #initrd=Ubuntu/initrd.lz quiet splash
        initrd=ubuntu-installer/amd64/initrd.gz quiet splash
        ENDTEXT
        #LABEL Install Ubuntu 14.04 Desktop
        #MENU LABEL Install Ubuntu 14.04 Desktop
        #kernel Ubuntu/vmlinuz
        #append boot=casper automatic-ubiquity netboot=nfs nfsroot=192.164.1.64:/var/lib/tftpboot/ubuntu-installer/amd64/
        #initrd=Ubuntu/initrd.lz quiet splash
        #ENDTEXT
        ===========================================================

        • syslog:

          Sep 30 15:04:01 ubuntu dhcpd: DHCPDISCOVER from fc:bb:14:2b:79:78 via eth0
          Sep 30 15:04:02 ubuntu dhcpd: DHCPOFFER on 192.168.1.66 to fc:bb:14:2b:79:78 via eth0
          Sep 30 15:04:05 ubuntu dhcpd: DHCPREQUEST for 192.168.1.66 (192.168.1.64) from fc:bb:14:2b:79:78 via eth0
          Sep 30 15:04:05 ubuntu dhcpd: DHCPACK on 192.168.1.66 to fc:bb:14:2b:79:78 via eth0
          Sep 30 15:04:05 ubuntu in.tftpd[5294]: tftp: client does not accept options
          Sep 30 15:04:45 ubuntu dhcpd: DHCPDISCOVER from fc:bb:14:2b:79:78 via eth0
          Sep 30 15:04:45 ubuntu dhcpd: DHCPOFFER on 192.168.1.66 to fc:bb:14:2b:79:78 via eth0
          Sep 30 15:04:45 ubuntu dhcpd: DHCPREQUEST for 192.168.1.66 (192.168.1.64) from fc:bb:14:2b:79:78 via eth0
          Sep 30 15:04:45 ubuntu dhcpd: DHCPACK on 192.168.1.66 to fc:bb:14:2b:79:78 via eth0
          Sep 30 15:05:43 ubuntu dhcpd: DHCPREQUEST for 192.168.1.66 from fc:bb:14:2b:79:78 via eth0
          Sep 30 15:05:43 ubuntu dhcpd: DHCPACK on 192.168.1.66 to fc:bb:14:2b:79:78 via eth0
          Sep 30 15:05:44 ubuntu dhcpd: DHCPDISCOVER from fc:bb:14:2b:79:78 via eth0
          Sep 30 15:05:44 ubuntu dhcpd: DHCPOFFER on 192.168.1.66 to fc:bb:14:2b:79:78 via eth0
          Sep 30 15:05:44 ubuntu dhcpd: DHCPREQUEST for 192.168.1.66 (192.168.1.64) from fc:bb:14:2b:79:78 via eth0
          Sep 30 15:05:44 ubuntu dhcpd: DHCPACK on 192.168.1.66 to fc:bb:14:2b:79:78 via eth0

  3. this is a single line “append boot=casper netboot=nfs nfsroot=192.168.1.64:/var/lib/tftpboot/ubuntu-installer/amd64/ initrd=ubuntu-installer/amd64/initrd.gz quiet splash” not two line.

    And “kernel Ubuntu/vmlinuz” should be “kernel ubuntu-installer/vmlinuz”

  4. Also give me the output of the following command

    ls -l /var/lib/tftpboot/ubuntu-installer/amd64/

    and

    ls -l /var/lib/tftpboot/ubuntu-installer/

  5. Still persisting error …..

    link for error snap:

    https://www.google.co.in/search?q=bad+archive+mirror+ubuntu+14.04&client=ubuntu&hs=PZI&channel=fs&source=lnms&tbm=isch&sa=X&ved=0CAgQ_AUoAmoVChMIsv7C1eCeyAIVyR-UCh3tgAyl&biw=1301&bih=640#imgrc=Vxd0AUO8W446JM%3A

    Listing :

    root@ubuntu:~# ls -l /var/lib/tftpboot/ubuntu-installer/
    total 16060
    drwxr-xr-x 14 root root 4096 Sep 28 19:57 amd64
    -r–r–r– 1 root root 10031612 Sep 28 20:00 initrd.gz
    -r–r–r– 1 root root 6403032 Sep 28 20:00 vmlinuz
    root@ubuntu:~# ls -l /var/lib/tftpboot/ubuntu-installer/amd64/
    total 27796
    dr-xr-xr-x 3 root root 4096 Sep 28 19:55 boot
    drwxr-xr-x 2 root root 4096 Sep 28 16:36 boot-screens
    dr-xr-xr-x 3 root root 4096 Sep 28 19:55 dists
    dr-xr-xr-x 3 root root 4096 Sep 28 19:55 doc
    dr-xr-xr-x 3 root root 4096 Sep 28 19:55 EFI
    -rw-r–r– 1 root root 21797287 Sep 28 16:37 initrd.gz
    dr-xr-xr-x 3 root root 4096 Sep 28 19:55 install
    dr-xr-xr-x 2 root root 4096 Sep 28 19:55 isolinux
    -rw-r–r– 1 root root 6403032 Sep 28 16:37 linux
    -r–r–r– 1 root root 161800 Sep 28 19:55 md5sum.txt
    dr-xr-xr-x 2 root root 4096 Sep 28 19:55 pics
    dr-xr-xr-x 3 root root 4096 Sep 28 19:55 pool
    dr-xr-xr-x 2 root root 4096 Sep 28 19:56 preseed
    -rw-r–r– 1 root root 42960 Sep 28 16:37 pxelinux.0
    drwxr-xr-x 2 root root 4096 Sep 28 21:31 pxelinux.cfg
    -r–r–r– 1 root root 235 Sep 28 19:56 README.diskdefines
    lrwxrwxrwx 1 root root 1 Sep 28 19:56 ubuntu -> .

  6. The output of ls -l ls -l /var/lib/tftpboot/ubuntu-installer/amd64/ shows that you are using ubuntu 14.10 server OS. So you should copy content from ubuntu 14.10 desktop to ls -l /var/lib/tftpboot/ubuntu-installer/amd64/. Because above post is tested to deploy desktop OS.

  7. Great article but not very effective,

    i did every step and triple checked it all. but without success.
    my pxeclient wont boot and keeps giving a ipxe error

    • This article is tested on Ubuntu-14.04-64-bit. So don’t worry, If you have any issue then send me error screen shot. I will give you solution.

      • that wont be nessecary ;)

        i already found the problem in the firewall at port 69, the dhcp settings and the rights to the tftpboot map :)

  8. Great article! I do have an issue where the PXE Boot screen keeps reloading on my client machine. I can see the options to Try and Install Ubuntu, but selecting one of them just refreshes the screen. Syslog shows the following entry on my tftpd machine when I select an install option on my client machine:
    Dec 30 05:30:02 NEBUCHADNEZZAR tftpd[4703]: tftpd: trying to get file: Ubuntu/vmlinuz
    Dec 30 05:30:02 NEBUCHADNEZZAR tftpd[4703]: tftpd: serving file from /var/lib/tftpboot

    Any ideas?

  9. CLIENT MAC ADDR: *************** GUID : (*********************************)
    CLIENT IP :192.168.2.232 MASK:255.255.255.0 DHCP IP:192.168.2.50
    GATEWAY IP:192.168.2.62
    PXE-E11:ARP timeout
    PXE-E11:ARP timeout
    PXE-E38:TFTP connot open connection
    PXE-MOF:Exiting Intel PXE ROM
    FATAL: Could not read from the boot medium! System halted

    hi..i tried this by making my vmware as my client.when i try to on my VM i got this error on screen.so please help asap.thank you

  10. CLIENT MAC ADDR: 00:00:00:00:00:00 GUID : (*********************************)
    CLIENT IP :192.168.2.232 MASK:255.255.255.0 DHCP IP:192.168.2.50
    GATEWAY IP:192.168.2.62
    PXE-E11:ARP timeout
    PXE-E11:ARP timeout
    PXE-E38:TFTP connot open connection
    PXE-MOF:Exiting Intel PXE ROM
    FATAL: Could not read from the boot medium! System halted

    • Can u please give me the output of following:

      ls -l /var/lib/tftpboot/ubuntu-installer/amd64/

      and

      ls -l /var/lib/tftpboot/ubuntu-installer/

      and

      cat /var/lib/tftpboot/pxelinux.cfg/default

  11. thank u HITESH….THIS IS THE OUTPUT
    vijay@vijay-OptiPlex-3020:~$ ls -l /var/lib/tftpboot/ubuntu-installer/amd64/
    ls: cannot access /var/lib/tftpboot/ubuntu-installer/amd64/: No such file or directory
    vijay@vijay-OptiPlex-3020:~$ ls -l /var/lib/tftpboot/ubuntu-installer
    ls: cannot access /var/lib/tftpboot/ubuntu-installer: No such file or directory
    vijay@vijay-OptiPlex-3020:~$ ls -l /var/lib/tftpboot/
    pxelinux.0 pxelinux.cfg/ Ubuntu/ vesamenu.c32
    vijay@vijay-OptiPlex-3020:~$ ls -l /var/lib/tftpboot/ubuntu-installer/amd64/
    ls: cannot access /var/lib/tftpboot/ubuntu-installer/amd64/: No such file or directory
    vijay@vijay-OptiPlex-3020:~$ ls -l /var/lib/tftpboot/ubuntu-installer/
    ls: cannot access /var/lib/tftpboot/ubuntu-installer/: No such file or directory
    vijay@vijay-OptiPlex-3020:~$ cat /var/lib/tftpboot/pxelinux.cfg/default
    DEFAULT vesamenu.c32
    TIMEOUT 100
    PROMPT 0
    MENU INCLUDE pxelinux.cfg/PXE.conf
    NOESCAPE 1
    LABEL Try Ubuntu 14.04 Desktop
    MENU LABEL Try Ubuntu 14.04 Desktop
    kernel Ubuntu/vmlinuz
    append boot=casper netboot=nfs nfsroot=192.168.2.62:/var/lib/tftpboot/Ubuntu/14.04/amd64
    initrd=Ubuntu/initrd.lz quiet splash
    ENDTEXT
    LABEL Install Ubuntu 14.04 Desktop
    MENU LABEL Install Ubuntu 14.04 Desktop
    kernel Ubuntu/vmlinuz
    append boot=casper automatic-ubiquity netboot=nfs nfsroot=192.168.2.62:/var/lib/tftpboot/Ubuntu/14.04/amd64
    initrd=Ubuntu/initrd.lz quiet splash
    ENDTEXT

  12. Just configured the DHCP service like you did but it wont start the service. Its just saying [fail] check syslog for diagnostics.
    I am a total noob at linux so please HELP! :-D

  13. i need help how to make dban pxe server allow to save logs on the network when finished wiping ???????????

  14. hey at first good guide thanks very much but i have a problem
    iget to boot into the pxe server looks exactly like the last pic above when i select install ubuntu nothing happens and when i select try ubuntu a timer of 10s starts to count down and when it hits 0 it starts over again.

    would be nice if you could help me with the problem

  15. Thanks to this article I was able to slot the final pieces of the puzzle together. I’ve created a bash script that goes through this entire procedure automatically – thus ensuring repeatability! I also have full associated guide and troubleshooting notes, for any who need.

    https:// github.com/taikedz/our-pxe

    Works on Ubuntu, can setup a PXE server to serve any Ubuntu-derived desktop (provided it still uses casper during the inital boot process)

        • Hi sorry for the question but can you be little brief on below

          do we have to runremaster.sh and setup=pxe.sh one again thanks in advance

          • Hi Dominic

            remaster.sh is only necessary if you want to pre-customize an ISO

            setup-pxe.sh should work with any Ubuntu ISO (except Ubuntu Server which has a few quirks) so you can roll with vanilla Ubuntu too. I dare say it may even work with Mint and Zorin, but I have not tested those.

            The PXE server itself can be any Ubuntu-based system, including Ubuntu Server.

            The most minimal command is

            bin/setup-pxe.sh -iso path/to/distro.iso -distro “My Ubuntu”

            The script will ask to confirm the rest of the parameters interactively.

          • Hi Taikedz,

            The script worked like a charm a million thanks you saved my day if it is not too much to ask can we add some kickstart to this repository? if yes can you please guide me.
            once again
            Thanks in Advance :D :D

          • Hi Dominic

            I have to revisit the kickstart stuff – it is in principle possible to add, but I burnt out when looking for workable instructions for ways to pass kickstart to Casper/Ubiquity

            I know from previous tests that it’s fairly easy to do with CentOS, though I tweaked my script heavily to target deploying Ubuntu. There should be a way to do a CentOS/Fedora setup with kickstart files, but as I said on another reply I’d need to revisit some old notes to find what the technique was there, when I have the time.

  16. Hi,

    I have set up the PXE server exactly as you have explained

    When it comes to booting up a client machine, I can get to the menu however if I try pressing enter to proceed with one of the boot options
    “Try Ubuntu 14.04 Desktop” or “Install Ubuntu 14.04 Desktop”

    I get no response.

    Any idea why this is?

    Thanks

    • Do you mean the timer restarts again (stuck at menu)?

      Check for typos in pxelinux.cfg/default file. Double-check, triple check. Consider everything as case-sensitive, down to rogue white-space characters.

      • Yes, you were right. Awesome guide. Is there a way to install Windows and Fedora in the same fashion?

        • I’d need to tweak this to set up something else like CentOS or Fedora etc, but most of the pony work is done now…. I’ll have to dig out my notes and revisit this when I have the chance….

          As for installing Windows like this I’m not sure. There’s a way to do it, but I suspect it would be a bit more involved. That said I have not yet tried…. it might be easier than I think.

  17. In the PXE boot screen, Try Ubuntu DOESN’T WORK but Install Ubuntu works.
    Why is that? Try Ubuntu drops me in Busybox (initramfs)$
    then it stops

    • I got that a few times whilst testing. It’s infuriating.

      You can switch to tty1 (Ctrl-Alt-F1) to see where the boot process stopped and use (Shift+Pg Up) to scroll backwards. You may see references to unable to load /dev/sr0 or the likes.

      If you are not using NFS, do so, it is required for casper, the installer technology Ubiquity relies on

      If you are using Ubuntu Server, don’t, this method will not work (this method depends on casper which is only in Ubuntu desktop variants)

      As always, double-triple check for typos in any files you’ve edited.

  18. I did it in the same way as you! But when I boot it only shows the labels. If I hit Enter nothing happens :-(

  19. sudo cp /media/casper/initrd.lz /media/casper/vmlinuz /var/lib/tftpboot/Ubuntu/

    gives this error message:

    cp: cannot stat ‘/media/casper/vmlinuz’ : No such file or directory

    dont know what to do, because I did it step by step in the same way.

  20. Hi Taikedz,

    Thank you for the response and once again ! I have a query after I configured the PXE server using the script everything worked fine till the server got rebooted due to faulty power cable post that I PXE installation is not working network boot is working I presume that we need to start some services for that to work as well correct me if I am wrong. once again thank you in advance.

    :D :D :D

  21. When I try to select an option in the pxe menu nothing happend… Syslog shows following: in.tftpd[1154] client does not accept options…

    I think its about this line in /etc/default/tftpd-hpa

    OPTIONS=”-l -s /var/lib/tftpboot”

    what is option -l and -s?
    anyone knows?

  22. Hi Dominic

    Apologies only now just saw your message.

    Not sure what you mean by “network boot is working” but PXE is not….. can you explain further?

    PXE server advertises itself via DHCP – hence the DHCP server component. If the target host is seeing and accepting a different DHCP server when it boots, then it won’t use PXE. Not sure what the best way to manage this is, but is more of a sysadmin thing than strict PXE. Segregate the host and PXE server from the main DHCP server to find out if this is indeed the scenario.

    Again, check my notes for extended troubleshooting tips

  23. Dumplingface — your comments are too spare. What says “sudo cd /mnt not found” ? What context? What action shappened before? Is this when booting, after booting, which tty; or is it during setup etc? Be more detailed and help may be possible.

  24. Hi all,

    I am fairly invested in getting a repeatable PXE setup going, so I am willing to give my tips and what I learned on my journey.

    Can I ask that anyone else do the same – saying you fixed your problem is nice for interactions, but we learn nothing. Please always detail what you did, what you expected, and what you got intstead; and when you resolve, detail why actually you got the error and what you did to fix it.

    Anyone working on this kind of stuff, you are welcome to add to the github.com/taikedz/our-pxe project (root/username/*.md or *.txt notes welcome), but elsewise, some notes on this thread would be most beneficial too!

    :-D

  25. I don’t find /usr/lib/syslinux/vesamenu.c32 and I did an apt-file search for it and came up empty.

  26. after successful installation of Ubuntu not able to connect to Ethernet, Ethernet port is not working but wifi device is working fine for me.

  27. Thank you for the excellent article. could you help me figure out a PXE error I get just after the dhcp connection completes?
    I tried doing things manually and also tried you setup-pxe.sh script but both end up in the same spot when I try to boot the client.
    Error:
    PXE-T02: B->No such file or director
    PXE-E3C: TFTP Error – Access Violation

Comments are closed.

Sponsored Stories