Symantec GHOST IMAGING FOUNDATION 7.1, Manual, Page: 176 / 189

Table E-3
Symantec GhostCast errors (continued)
Solution Problem
This is usually caused by a connectivity problem between
the server and the client. To determine the source of the
problem try the following:
■
Verify the spelling of the session name on both the client
and the GhostCast Server.
■
Check all physical connections, including cabling, hubs,
routers, switches, and so on for physical problems.
■
Verify that any routers present between the server and
the client are configured properly and have GhostCasting
enabled.
■
Check the Wattcp.cfg file for a valid IP address and
subnet mask if you are using static IP.
■
Confirm that a network communication topology
problem exists by connecting the GhostCast Server and
client to a dumb hub or cross-over cable. Then use, static
IP to try to complete the task.
You can also try pinging the IP address of the client
computer from the server computer.
If you are not able to ping the client, there is a
communication problem, and IP packets are not being passed
between these computers.
To ping the IP address of the client computer:
■
Start the client computer.
■
On the Symantec Ghost main menu, click GhostCast and
select one of the following:
■
Unicast
■
Direct Broadcast
■
Multicast
Do not enter a session name. Stop at the dialog box
requesting the session name. This will initialize the
IP address.
■
Ping the client from the server.
Symantec Ghost times-out
after I type a session name.
Add a RECEIVE_MODE=X value to the Wattcp.cfg file. Add
RECEIVE_MODE=5 first, then try 6.
If you are GhostCasting across routers or switches, you must
enable a GhostCasting protocol on these devices.
For more information on GhostCast protocols, refer to your
router or switch documentation.
When I begin sending data
via GhostCasting, the session
fails or times out.
Troubleshooting
Symantec GhostCast errors
176