How To Verify Access To The TFTP Service From A Client Computer

Article:TECH109612  |  Created: 2007-01-04  |  Updated: 2007-01-28  |  Article URL http://www.symantec.com/docs/TECH109612
Article Type
Technical Solution

Issue



How To Verify Access To The TFTP Service From A Client Computer

Symptoms
You want to verify that the TFTP service on a LiveState Delivery or iCommand server is functioning
  • You want to test whether clients can access the TFTP service on a LiveState Delivery or iCommand server


Solution



To verify that the LiveState Delivery TFTP service is accessible from a client and functioning correctly, you can:

1. Configure a client to perform a PXE boot, and watch the client console during a reboot.
If the TFTP service is running on your server, and your DHCP scope options are properly defined,
then you should see a screen similar to the following (this example shows boot.ovl from LiveState Delivery):

    CLIENT MAC ADDR: 00 0C 29 87 3B 74 GUID: 564D9E1C-DA58-9506-C539-BD3DE8873B74

    CILENT IP: 192.168.1.14 MASK: 255.255.255.0 DHCP IP: 192.168.1.2
    GATEWAY IP: 192.168.1.1
    LSD;BA;Version: 5.294;SDA;5.6;

2. Run a Command-Line call to tftp.exe from within Windows a client computer. For example, open a Command Prompt and run this:
tftp -i get /etc/integra/tftp/boot.ovl

If the command succeeds, you will have a copy of boot.ovl in the current working directory.




Technical Information
If you have an issue with the tftp download of the boot overlay file, here are a couple of quick configuration tests to try:


1. If a "TFTP Error: Access Violation" error appears when a client computer is attempting to download boot.ovl, set DHCP option 13 (Bootfile Size) to 1 and try again. Certain types of DHCP servers may supply boot file names that are not terminated in a null character. Intel Architecture Labs PXE 2.1 addresses the null terminated boot file names, but fails to work correctly if the DHCP boot file size option is not present when using Intel Boot Agent 4.0.19. This issue was corrected in Intel Boot Agent 4.0.22. Customers using IBA 4.0.19 and running into this issue can also work around it by setting DHCP boot file size tag 13 as a non-zero value (ideally the size of the boot file).

2. If the boot.ovl download still does not succeed after previous attempts at troubleshooting, and your environment does not include the Pre-OS Locator service, set DHCP option 128 to the IP address of the TFTP server and try again.



Legacy ID



2007100411252760


Article URL http://www.symantec.com/docs/TECH109612


Terms of use for this information are found in Legal Notices