Error: "Application Error 503. Connection timed out with Ghost code 19945" while creating an image file
|Article:TECH107435|||||Created: 2000-01-26|||||Updated: 2013-10-30|||||Article URL http://www.symantec.com/docs/TECH107435|
You are using Ghost Multicast Server or GhostCast Server to create an image of a disk or partition and save it on the Ghost server computer. While Ghost is transmitting the image, you see the message "Application Error 503. Connection timed out with Ghost code 19945" at the client computer and the message "Connection reset by peer" or "Application Error 502. Connection timed out with Ghost code 19945" at the server computer. The code might be different on your computer, such as 19922.
There are multiple possible causes.
This problem often happens when the server computer does not have enough disk space to store the image file or the storage location is inaccessable. To resolve the problem, store the image file on a different partition/harddrive or free up sufficient disk space on the server computer.
Other causes and solutions
- This problem sometimes happens when mapping a drive to a different server. To resolve the problem, use a UNC path for the server, or install Ghost to the second server and run Ghost from there.
- This problem has been seen when using the wrong DOS drivers for the network interface card (NIC), such as drivers that are for a different model of NIC. Obtain the correct DOS drivers from the NIC manufacturer, update Ghost to use the new drivers, and then create a new boot floppy disk that uses the new drivers. See the document Adding or modifying NIC templates in the Ghost Boot Wizard.
- If the client computer uses the D-Link DFE500TX NIC, using the NIC's packet drivers instead of the NDIS drivers sometimes resolves this problem.
- This problem has been seen when the client computer has more than one NIC. See the document "How to use a different NIC on a client computer that has multiple NICs."
- This problem has been seen when the server computer has more than one NIC. Ghost does not support running Ghost Multicast Server, GhostCast Server, or Ghost Console on a computer that has multiple NICs. To resolve the problem, remove all NICs but one before running Ghost Multicast Server.
- This problem has been seen when the server computer has more than one IP address. To resolve the problem, remove all IP addresses but one before running Ghost Multicast Server.
- Try changing the compression level. For instance if you are using High compression, switch to Fast.
Error "Close socket fail..." and "...19922 Multicast read error" while running Ghost Multicast
Error: "(19922) Connection reset by server" or other problems when restoring a split image file
Error: "RML_SEND FAILED" or "RML_BIND FAILED" When Trying to Accept Clients on Ghost Multicast Server
Article URL http://www.symantec.com/docs/TECH107435