Ghostcasting and QoS

[trptplayer1]

Hello,

I'm trying to ghostcast across subnets. The ghostserver is connected to a 4506 Cat Switch. Most clients are connected to 3560, 3550, and 2950 switches. I know that at one building multicasting won't work becuase multicasting has to be turned on. We have though in the past been able to use directed broadcast with the ghostcast server app. It has worked well. I'm wondering if it is possible that our new QoS could be keeping the service to actually run. The error message I get is "waiting for ghostcast server to start" which means the computers are connected to the server without problems, but the traffic isn't making it across the subnet. We don't have any traffic policing/shaping. Our VOIP traffic is given priority. Or possibly ACL policies. Although I dont' think so. Any help is appreciated.

Thanks,

Dan Christ

Manteno CUSD#5

Manteno, IL

[ebreniz]

know that the Ghosting control channels are 224.77.1.0 and 224.77.0.0 the data is sent to other multicast addresses that are ramdom within a particular range.I found the Symantec Ghost Implementation Guide:

ftp://ftp.symantec.com/public/english_us_canada/products/ghost/manuals/ghost75implement.pdf

Chapter 14 talks about GhostCasting and IP addresses but I could not find anything there about

what multicast addresses are used to multicast data after the control session are set up. I spoke to my friend who told me that is is possible to configure what mcast addresses are used on the Ghost Servers to send data to and that otherwise the mcast address is rendomly chosen from a known range.

[trptplayer1]

Thanks so much for the info! I'll check into it. It has been tricky in the past for them to ghost. I just started here and in the past they have used directed broadcast. But that isn't good for large labs. We would much rather prefer using multicasting.