Support Home   |   Supported Products A to Z

Symantec.com > Enterprise > Support > Knowledge Base

Knowledge Base X
How Ghost Multicasting communicates over the network  PRINT THIS PAGE
Search

Advanced Search Options

Question/Issue:
Other Support Resources
This document discusses how Ghost performs multicasting for sending an image from the server to the client.
l Support Forums
Ask an expert. Join
collaborative product
Solution:
discussions within our Forum
This document discusses the following subjects:
community.
NOTE: This document is provided for the Information Technologies professional. It requires knowledge of
l Manage Cases Online
advanced networking concepts. Symantec Technical Support does not provide assistance with this document. If
Submit and manage your
you need assistance with information contained in this document, please consult your networking
support cases using
documentation or your Information Technologies department.
MySupport.
l Introduction - How the Ghost Server and Ghost Client communicate over a network
This section is a general discussion of how Ghost implements the TCP protocol. l Contact Technical Support

l Part 1 - How Ghost starts the session Find the support phone number

This section provides the steps to make Ghost initiate communications over the network. for your region.

l Part 2 - How Ghost sends image data

This section describes how Ghost communicates over the network after the Ghost Server's Auto Start criteria Was this article helpful to you?
have been met.
l Part 3 - How Ghost closes the session j Yes    n
k
l
m
n j No
k
l
m
This section describes how the Ghost Server and Ghost clients communicate with each other to indicate that the
copy process is concluded and to close the session. If any information was unclear, or

l More information on packets, IP addresses, UDP/TCP protocols, and ports the information you were seeking

This section includes a table that illustrates the sequence of packets sent in Parts 1 through 3, and charts was not provided, please let us

illustrating additional information. know. Your feedback will help us

improve this service.

(Enter comment here) 5

Introduction - How the Ghost Server and Ghost 6
Client communicate over a network
Ghost Multicast communicates through both UDP and TCP. When using the Windows version of Ghost Multicast, the
(Optional Email Address)
TCP stack at the Ghost Server is provided by Windows. At the Ghost Client, the TCP stack is provided by Ghost.
NOTE: Communication across the network requires the proper Network Interface Card (NIC) drivers for each
Submit
computer. Discussion of NIC drivers is beyond the scope of this document. For more information, refer to your
NIC documentation and see the document: How to add or modify NIC templates for Multicast Assist. You can NOTE: Comments entered here will
also search the Ghost Knowledge Base for the model number of your NIC. NOT receive support services. If
you need Symantec Enterprise
UDP compared to TCP product support, please click here.
Ghost uses a combination of UDP and TCP. TCP cannot be used effectively for multicasting since the TCP protocol is
designed for reliable communications between two end points, not between a group of client computers and a server.
There are no multicasting protocols that use TCP.

UDP is fast and allows Ghost to stream the data: That is, Ghost is not required to wait for an acknowledgment before
sending the next packet.

Ghost Multicast Server, GhostCast Server, and Ghost Console require that the network switches and routers be IGMP-
capable. When the routers or switches are not IGMP-enabled, Ghost may flood the network with packets or not work
at all. See the document Ghost compatibility with IGMP.

How the Ghost Client communicates with TCP

Ghost.exe includes software for communicating through TCP. It packages the information into TCP and sends it to the
drivers for the Network Interface Card (NIC). The NIC then sends out the packets. Similarly, when the Ghost Client
computer receives a packet, the NIC forwards the information to the Ghost Client.

How the Ghost Server communicates with TCP

When run in Windows, the Ghost Multicast Server does not include software for communicating through TCP. Instead,
it relies on Windows software. Information is sent to the RML, which packages it for Winsock. Winsock packages the
data into TCP and sends the data to the drivers for the Network Interface Card (NIC). The NIC then sends out the
packets.

Similarly, when the Ghost Server computer receives a packet, the NIC forwards the information through Winsock and
RML and then to the Ghost Server software. RML assigns "ports" to Windows applications to identify which application
to send the information to.

Addressing
The Ghost Server and the Ghost Clients recognize each other by their IP addresses. Messages are sent to one or
more of the following addresses:
l The Ghost Client's IP address
l The Ghost Server's IP address
l A Broadcast IP address in the form: 226.77.255.255.xxxx
l A Multicast IP address in the form: 224.77.255.255.xxxx

The details of addressing vary according to the IP Class of addresses on the network. On a network using Class C
addresses:
l The "255" figures in the address (as shown above) represent any value between 0 and 255, but not 0
nor 255.
l The "xxxx" in the address represents the port number assigned to the application on the server or client
computer.

The computer is identified by the 255.255.255.255 portion of the address. The application at each computer is
identified by the xxxx portion of the address (the port address). For instance, in the address 123.46.52.105.6666,
123.46.52.105 designates the specific computer and 6666 designates the specific application on that computer.

The port address is a number automatically assigned to applications by the TCP protocol. Each application has a
different number so that incoming packets can be routed to the appropriate application. The Ghost Server's port
number is assigned by RML (a part of the TCP stack).
Image Verification
Packets - All packets sent by means of the Ghost Multicasting protocol are protected by a checksum.
Images - An image file can be verified during the image creation only by using the Ghost verify function (that is, the
switches -VDW and -VFY). The switch -VDW verifies disk writes and the switch -VFY verifies each write to an image file
(not spanned images). To verify an image after it has already been created, use the Ghost integrity check. See the
document How to handle a corrupt image file.

When the Ghost server and Ghost client cannot communicate

When the Ghost Server cannot establish a connection with one or more of the Ghost Clients, the Multicast option on
the Ghost client appears dimmed, or Ghost displays an error message (or stops responding) and cannot continue. To
resolve connection problems, see the "Troubleshooting Ghost Multicast Problems" section of the document How to
create and troubleshoot a Multicast client boot disk.

Part 1 - How Ghost starts the session

In the handshaking process, the computers identify each other and then exchange addressing information. To begin
the handshaking process, the Ghost Client initiates contact with the Ghost Server by sending a Broadcast message.
Subsequent messages in this stage are addressed to each computer's IP address and are for:
l Identifying the Ghost Server and Ghost Client computers.
l Exchanging address information, such as the exact Broadcast IP address and Multicast IP address to be
used during the session.
l Verifying what data will be sent.

Step 1 - Setup the Ghost Server computer

This is the computer on which you installed Ghost, and selected Server (instead of Client) during the installation.
1. Open Ghost Multicast Server.
2. Configure the Ghost Multicast Server. This includes typing in a Session Name, selecting an Image file
that will write over the Ghost Client, and selecting an Auto Start option. For more information, see
Chapter 4 of the Ghost User's Guide.
3. Click Accept Clients. This prompts Ghost Server to watch for network packets that are addressed to
226.77.255.255:xxxx (for an explanation of this number, see the section "Addressing.")

Step 2 - Setup the Ghost Client computer

This is the computer on which you installed Ghost, and selected Client (instead of Server) during the installation. Or
you did not install Ghost on this computer. Instead, you booted up the computer from a floppy disk, and ran
Ghost.exe from the floppy disk.
1. Open Ghost and select OK.
2. Select Multicasting.
3. Type in the Session Name.
4. Click OK. This prompts Ghost Multicast to send a Broadcast packet (that includes the Session Name) to
the address 226.77.255.255:xxxx.

When the Ghost Server reads the packet sent by the Ghost Client, it determines whether the Session Name in the
packet matches the Session Name you typed in at the Ghost server. If there is a match, the Ghost Server replies to
the Ghost Client's IP address. This reply contains the following information:
l The IP address of the server.
l The port number for the RML session.

NOTE: The port numbers will vary. For more information, see the section "Addressing."

The Ghost Server and Ghost Client then finish exchanging addressing information and verify what image data will be
sent from the Ghost Server to the Ghost Client (this image data is the same for all Ghost Client computers attached to
this session.)

To attach each Ghost Client to the session, repeat steps 1 through 4 for each Ghost Client computer.

Step 3 - Select options at the Ghost Client computer

The Ghost Client now displays choices for which disk or partition to write over, and then whether and how to resize the
destination disk or partition, and other miscellaneous options, depending on the choices you make during this session.

When you have completed making the choices, the Ghost Client will display a message similar to "Proceed with image
file creation?" The answer defaults to No. Answer Yes to have the Ghost Client notify the Ghost Server that it is ready
to receive images.

The Ghost Server continues to establish connections with each Ghost client computer until the Multicast Auto Start
criteria have been met, or you click the Send button at the Ghost Server. Multiple clients can go through this process
in parallel.

Part 2 - How Ghost sends image data

Once the Auto Start criteria have been met (or you clicked Send Now at the Ghost Server), the Ghost Server is ready
to send the image data. Here is the sequence of events:
1. The Ghost Server identifies the slowest Ghost Client in the session and selects that client as the Master Client.
It sends the data packets to the IP address of the Master Client and "echoes" that data to the Multicast IP
address.
2. Each Ghost Client listens for that address in addition to its own address. When it sees a packet sent to the
Multicast address, the packet is processed as though it were sent to the client directly.
3. The Master Client sends regular acknowledgments indicating the progress of the session. It sends
acknowledgments to the Ghost Server's IP address, and echoes that data to the Broadcast IP address. It
usually acknowledges every second packet.

If a client falls behind processing or receiving packets, it sends a message to the server.
l If possible, the server resends the missing packets (it can only resend them if they are in the server's buffer).
l If the client is far enough behind, and the missing packets are still in the server's buffer, the server will resend
the missing packets and make the client the Master Client.
l If it is not possible to resend the packets, the server cancels the client's participation in the session, displaying
the error message "RML Connection Reset by Server" at the client computer.

Part 3 - How Ghost closes the session

Once all the image data has been sent, the Ghost Server initiates the end of the session by sending a message to the
Broadcast IP address. All the Ghost Client computers acknowledge this by sending a message to the Ghost Server's IP
address. In Ghost versions prior to 6.0, additional end-of-session messages might be sent.

Closing the session usually requires two or four packets:

 1. To start the close of the session, the Ghost Server sends a Broadcast message indicating that it has no more
data to send.
2. All the Ghost Clients send a packet acknowledging this.

NOTE: If a Ghost Client computer fails to send the acknowledgment, the server assumes that the client failed
during the session and displays that client as failed. This is usually a good assumption. The client could have
failed further back in the session. If the client could not send anything to the server, it could not have notified
the server of any problems, and the server wouldn't know that the client had failed until the server failed to
receive the acknowledgment.
3. After sending an acknowledgment, the Ghost Client sends a "session complete" packet to the server.
4. The Ghost Server sends a packet to the Multicast address acknowledging the first "session complete" packet it
receives.

More information on packets, IP addresses,

UDP/TCP protocols, and ports
Table of packets sent
The following table illustrates the sequence and protocol in which packets are sent.

All messages are sent in UDP except Multicast messages, which are TCP.

How to read the table

Each row indicates a packet sent. Read the steps in numerical sequence. The sequence is indicated by the number in
parentheses, such as (1), (2,), and so on. Note that the steps do not follow a consistent pattern between left and right,
because not all packets are acknowledged.

GHOST CLIENT Direction GHOST SERVER

and
Protocol
Handshaking (1) Ghost Client sends a ----> (2) Ghost Server watches
The client and packet addressed to the UDP for packets addressed to
server exchange Broadcast IP address the Broadcast IP address
addressing 226.77.255.255.xxxx 226.77.255.255.xxxx. It
information. reads the packet and
Information sent: compares Session Names.
This process l Session Name, as

occurs for each typed in at the Ghost

Ghost Client Client.
computer. l The IP address of the

client, including the

client's TCP port number.
(4) Ghost Client receives <---- (3) If Session Names
the packet. UDP match, Ghost Server
replies to the Ghost
Client's IP address, to
identify itself to the
Ghost Client.

Information sent:
l The IP address of the

server, including the

server's RML port number.
(5) Ghost Client sends a ----> (6) Ghost Server receives
packet addressed to the UDP the packet.
Server's IP address and
RML port.

Information sent:
l Ghost Client is

currently in a wait state.

(8) Ghost Client receives <---- (7) Ghost Server replies
the packet and displays UDP with a message to the
any choices available to client's IP address.
the user, such as which
disk or partition, and disk Information sent:
or partition size. l Nature of the task.

l Address that will be

The user answers all used:

questions. The last 224.77.255.255:xxxx
question answered is
whether to proceed.
(9) Ghost Client sends a ----> (10) Ghost Server
packet back to the server UDP receives the
as an acknowledgment. acknowledgment and
displays the client's IP
address in the "Connected
Information sent: Clients" box.
l Ghost Client is ready to

receive the data.

(12) Ghost Client <---- (11) Ghost Server sends
 receives the packet. UDP a message instructing the
client to wait for further
information. The Ghost
Server continues to
establish connections
with other Ghost Client
computers, until the
Multicast Server's Auto
Start criteria are met.
Communications (2) Each Ghost Client <---- (1) The Ghost Server
after the Auto listens for messages sent TCP sends data packets to the
Start criteria to 224.77.255.255:xxxx, Multicast address
have been met. in addition to its own <---- 224.77.255.255:xxxx, and
Or after the Send address. It processes UDP the same message to the
button is clicked. packets sent to Master Client's IP
224.77.255.255:xxxx as address.
though they were sent to
the client directly. Information sent:
l Image data.

(3) For approximately ----> (4) Ghost Server receives

every second packet sent UDP the packet.
by the Ghost Server, the
Master Client sends an
acknowledgment to the ---->
Ghost Server's IP address TCP
and the same message
to the Broadcast IP
address.

*NOTE: If a Ghost Client

misses a packet, it sends
a message to the Server
IP address, and the same
message to the
Broadcast IP Address.

Information sent:
l Acknowledgments of

data received.
Closing the (2) All Ghost Clients <---- (1) The Ghost Server
session receive the packet. UDP sends a packet to the
Sends the first Broadcast address
two packets 226.77.255.255:xxxx
indicated, or all
four. Information sent:
There is no more data to
be sent.
(3) All Ghost Clients ----> (4) Ghost Server receives
acknowledge the packet, UDP the acknowledgment. In
addressed to the Ghost some cases, Ghost
Server's IP address. Multicast stops, and the
session is ended. In other
situations, the session
continues for two more
packets.
(5) All Ghost Clients ----> (6) Ghost Server receives
send a "session UDP the packet.
complete" packet to the
server's IP address.
(8) All Ghost Clients <---- (7) Ghost Server sends
receive the packet. TCP an acknowledgment to
224.77.255.255.xxxx for
the first "session
complete" packet it
receives.

Additional information
Here is another way of looking at communications between the server and client computers.

High Level Protocol used by the Ghost Enterprise Console and the Ghost Client
When the client computer is running Windows, the Ghost Client is NGctW32.exe. After the client computer has
restarted into the hidden Ghost boot partition, the Ghost Client is NGctDOS.exe.

Sent Source Destination Destination Type Volume

By Port Address Port
Stage 1 Client Varies 229.55.150.208 1345 UDP Low
Server Server 1345 Client IP Varies UDP Low
discovery
 Stage 2 Client Varies Server IP 1346 UDP Low
Status Server 1346 Client IP Varies UDP Low
update
Stage 3 Client Varies Server IP 1346 TCP Low
Executing Server 1346 Client IP Varies TCP Medium
task

High Level Protocol used by the Ghost Multicast Server & the Ghost executable
The Ghost executable is Ghost.exe, running on the client computer.

Sent Source Destination Destination Type Volume

By Port Address* Port
Stage 1 Client Varies 224.77.0.0 6666 UDP Low
Server Server 6666 Client IP Varies UDP Low
discovery
Stage 2 Client Varies Server IP Varies TCP Low to
Medium
Status Server Varies Client IP Varies TCP Low to
update Medium
Stage 3 Client 7777 Server IP Varies UDP High
Executing Server Varies 224.77.1.0 7777 UDP Low
task
Server Varies 224.77.xxx.xxx 7777 UDP High

*By default, the IP address 224.77.xxx.xxx is a random address between 224.77.2.0 and 224.77.255.255. Starting
with Ghost 6.0, the address can be set at the Multicast server to be any desired multicast address, using the -M switch.
This switch is documented in the Ghost 6.01 User's Guide on page 133, and in the Ghost 6.03 User's Guide on page
162.

Available Translations:
--choose a language--- 6

Document ID: 1999033015222425

Last Modified: 01/31/2007
Date Created: 03/30/1999
Operating System(s): DOS, Windows 95, Windows 98, Windows NT, Windows 2000, Linux, Windows ME, Novell NetWare
Product(s): Symantec Ghost 7.0, Symantec Ghost 8.0
Release(s): Ghost 7.0 [All Releases], Ghost 8.0 [All Releases]

Site Index · Legal Notices · Privacy Policy · Site Feedback · Contact Us · Global Sites · License Agreements

©1995 - 2010 Symantec Corporation

converted by Web2PDFConvert.com