1. Ensure that the NIC Template being used has the most current DOS drivers available. See the document Adding or modifying NIC templates in the Ghost Boot Wizard for more information about updating NIC templates.
2. Use Live Update to update Ghost Solution Suite to latest version available. At the time of this document, the latest version of Ghost 11.0 was 220.127.116.113 and the latest version of Ghost 11.5 was 18.104.22.1681. For more information about how to apply the Live Update:
3. Use MS-DOS instead of PC-DOS. For more information about importing MS-DOS files, see the document How to import MS-DOS into Symantec Ghost.
4. Apply a Static IP address to the client machine, run a Refresh Configuration task from the console, and re-execute the task.
5. Apply a Static IP address to both the Ghost Console and client machines and then connect the two machines with a simple "dumb" hub. If this corrects the issue, there is a network problem that's preventing you from pulling an IP address.
6. Add a timeout period of 60 seconds using the wattcp.cfg file. See the document How and when to modify the Wattcp.cfg file for more information about wattcp.cfg.
7. Ensure that the Network Boot option is last in the boot order.
8. Update the BIOS on your client computers to the latest version offered by the manufacturer.
9. Ensure that the network interface card (NIC) is not in IRQ conflict with another device on the system. If the NIC is sharing an IRQ, update your NIC template to include IRQCFG.EXE. The presence of IRQCFG.EXE should force Ghost to resolve the IRQ conflict. Fore more information about how to modify your NIC template to include IRQCFG.EXE, see the document How to create a Network Boot Package to resolve IRQ conflicts.
10. If the issue appears when using a Ghost Boot Disk with the Ghost Cast Server, create a Windows PE disk and perform your imaging operation with ghost32.exe. For more information on how to create a Windows PE disk:
11. When the client machine begins to boot to DOS, tap the F8 key to initiate a step-by-step confirmation. The purpose of this step is to slow the boot process down. Answer Yes to all queries and note any error messages received. For Ghost Console tasks, the last thing to load will be NGCTDOS.EXE. For Console tasks, proceed as follows:
- Answer "No" when asked to start NGCTDOS.EXE. When you answer "no," you'll be taken to a command prompt. At the command prompt, type ghost.exe and attempt to manually join the Ghost Cast Server session that was established by the Ghost Console.
- Answer "Yes" to NGCTDOS after a few seconds. Sometimes, slowing the task down will allow you to connect to the Ghost Cast Server session.
12. Reboot the DHCP Server.
13. If none of the above help to identify or resolve your issue, please fill out the attached Ghost Workbook and contact Symantec Technical Support.
How and when to modify the Wattcp.cfg file
How to update Ghost Solution Suite to version 22.214.171.1243
How to import MS-DOS into Symantec Ghost
Adding or modifying NIC templates in the Ghost Boot Wizard
How to build a Windows PE [Vista] CD/DVD that contains Ghost32.exe and then join a client machine to a Ghost Cast Server session to create or restore an image file.
How to create a Network Boot Package to resolve IRQ conflicts
Imported Document Id