Symantec Ghost client disconnects from console when too many "client initiated" tasks are created.
Symptoms You have a client that has a lot of client initiated tasks or you use long task names and at a certain point, you add a task and the client disconnects. If you remove a task, the client will reconnect.
There is an implicit limit due to the design of the protocol being used to transfer the list of tasks to the client. The list of tasks is sent in the regular status UDP packet. Due to the large size, the packet will be fragmented. Windows TCP/IP will start having problems reassembling the fragmented packet after a certain point which is not defined as yet. In addition, DOS clients would not support fragmented UDP packets at all.
At this point, Symantec is not be able to support a large number of client initiated tasks, due to the limits imposed by the chosen protocol for the task list update. There is no magic number, but after a certain point, the message will not be able to reach the client. Each version of Ghost has a limit and the newer the product is that you have, the more characters are allowed.
Imported Document Id
This is machine translated content
Login to Subscribe
Please login to set up your
For security reasons, your link to this document has expired. Please click on the attachment link to access this file.
The attachment that you are looking for no longer exists.
There has been an issue retrieving your attachment. Please try again.
Currently server is down.
Didn't find the article you were looking for? Try these resources.