How to troubleshoot the 10030 error message.

Article:TECH110226  |  Created: 2008-01-07  |  Updated: 2014-01-16  |  Article URL
Article Type
Technical Solution




You are receiving a 10030 error message and need to know how to troubleshoot the issue.

When you try to join a Ghost Cast Server session manually, using a boot disk on the client computer, a 10030 error appears. A Ghost Console task might also produce the error.



The 10030 error message indicates a communication problem between the Ghost Console computer and the Ghost Client computer.


This error has a variety of causes and no one solution will correct it. Proceed through the following steps to troubleshoot the problem.

  1. The GhostCast Server requires that UDP ports 6666 and 7777 be open in any firewall or AntiVirus software.
  2. Ensure that the multicast traffic is not being blocked by a router or switch in your environment.
      • If you are trying to join a GhostCast Server session using a Ghost Boot Disk, supply the IP Address of the Ghost Server to the client. You can specify the IP address on the same page in Ghost that you use to enter the session number you want to join. If specifying the IP Address of the Ghost Server gives the same error message, there is a likely multicast configuration issue on your network.
      • For Ghost Console tasks, use the -jaddr=ipaddressofconsole switch in the Advanced button on the Clone tab of your task to specify the IP Address of the Ghost Server. If specifying the IP Address of the Ghost Server in the task gives the same 10030 error message, there is a likely multicast configuration issue on your network.
      • Instead of selecting Multicast, select Unicast. If "Unicast" is working, then multicasting is either being blocked or has not been properly configured.
  3. Ensure that no 3rd party programs are blocking the Ghost communications.
      • If the third-party program has an exclusions list, such as "McAfee VirusScan 8.0i", fix the problem by adding "Ghostsrv.exe" to the exclusions list. For more information on this issue, see the document: "Error: 10030 - "Unable to establish connection with session" when using McAfee Anti-Virus 8.x." at:
      • If the third-party program uses a rule that blocks IRC communication or UDP traffic on ports 6666 or 6667, such as "ePolicy Orchestrator " (ePO), modify the rule in ePO to permit Ghost communications or add a new rule for Ghost that supersedes the blocking rule.  If not applied through ePO, changes to the managed computers will be overwritten.
      • This problem has also been seen with the "BlackICE PC Protection program." This program includes a firewall.
      • If you are using "Windows PE" as a pre-OS, the Windows Firewall could be enabled and blocking Ghost traffic.
      • Note: Simply disabling the Antivirus and the Firewall software may not be enough to correct this error. The software needs to be configured to allow Ghost to communicate.

  4. Update the network driver template.
      • If you are using a DOS pre-OS, download the NDIS2 drivers for your network card from the manufacturer's Web site and create a new Network Interface Card (NIC) template. For more information about creating DOS NIC templates, see the document: "Adding or modifying NIC templates in the Ghost Boot Wizard." at:
      • If you are using a Windows PE pre-OS, download the Microsoft Vista drivers for your network card. NOTE: When adding a WinPE NIC driver to Ghost, it can be important to return to the Boot Disk Wizard and VERIFY that the driver is still checked after completing the Boot Wizard. The driver name in the NIC drivers section of a driver list has been shown to come unchecked at times. For Microsoft downloads, see the following Web site:
  5. Can you reproduce the problem when you connect the Ghost Console and the Ghost Client by using a simple network?
      • For more information about how to set up a simple test network, see the document: "How to Set up a Simple Network." at:
      • If the problem is corrected with the simple network, then your production network is the likely source of the problem.
      • If a Ghost session starts and stalls out after transmitting the image for a few minutes and you have a RAID array you may be writing the image faster than the RAID controller can write. Check the RAID buffer speed and set the network throughput to about 10mg below the RAID buffer speed.
  6. Remove the Ghost Console and the Ghost Client from the domain and add them both to a workgroup.
      • If this corrects the error, there may be a Group Policy Object (GPO) on the domain that is causing the connection problem. Locate the GPO and either disable it or modify it to ignore Ghost communication.
  7. Copy the image file directly to the computer running the GhostCast Server.
      • The problem can be caused by a switch or router between the server and the computer that the image is being stored on, when that switch or router has not been configured for Multicasting. If that is the case, or if the problem is caused by some other path problem, putting the image on the same computer as the Ghost Console should prevent this error.
      • If the error occurs during the image create process, try storing your image on the same computer that is running the GhostCast Server. If this is successful, there could be a problem with the network share you originally tried to use as the image repository.
  8. Assign full control of the Image Repository to everyone.
      • If this corrects the issue, change full control from "everyone" to the specific user that will be signing into the computer running the Ghost software.
  9. If the problem persists after performing steps 1-8, gather the following information and contact Symantec Technical Support at:
      • A Wireshark network trace will be required. Install Wireshark on the computer running the Ghost Tools and start the network trace. When the network trace has begun, repeat your imaging process. When the client fails with the 10030 error message, stop the network trace and send the resulting log file to Symantec Technical Support.
      • A System Information Report from the Ghost Console and any clients that are receiving this error.
        • To obtain the System Information report, click Start > Run
          1. Type msinfo32.exe.
          2. Save the resulting report with a .NFO file extension.
      • From the Ghost Server, gather C:\Program Files\Symantec\Ghost\ngserver.log.
      • From the Ghost Client, gather C:\Program Files\Symantec\Ghost\ngctw32.log.
      • Fill out the attached Ghost workbook with as much detail as possible.


"Symantec Technical Support" at:


Workbook_Enterprise--gss2.0.doc (441 kBytes)

Legacy ID


Article URL

Terms of use for this information are found in Legal Notices