Ghost Solution Suite

Hello,

I'm trying to use Ghostcast 8.2 through the network using a network switch.
Client Pc is booted using a floppy disk with a fixed IP address, the server is ready to receive client connections.

When I start the client, then Ghostcast, Uincast, I enter the session name but the client never finds the path to the server.

If I use a crossed wire cable between the server and the client the session is immediately recognized (prooving the server is ok)

I've tried several switches : 3com office connect, HP Super Stack and another small switch it never works.

What's wrong with that way of handling the Ghostcasting? Switches work fine btw, I'm currently connected on one of them).

Thanks!

I had a similar problem with a 3COM switch on my network until I turned off the multicast filtering and broadcast storm control features on the switch. You may want to log into your switch (if possible) and see what kinds of things it can do.

> 3com office connect

Ah, but what kind? The bulk of the OfficeConnect range are unmanaged switches, and they tend to all work just fine with Ghost (I'm looking at a Gigabit switch 8 sitting here on my desk and I had an 8-port 10/100 in the same spot two years ago). It's the "clever" managed switches that tend to be problematic.

If Ghost never finds the GhostCast server at all, then the problem is likely as Daniel helpfully suggested, that there is a configuration setting to filter multicast and for some reason it's off.

After you have enabled multicast, depending on how clever the switch tries to be about multicast traffic, you may have more problems. Layer 2/3 switches build their knowledge of multicast distribution groups by "sniffing" for a particular of protocol called IGMP, which is how hosts register to listen to a multicast group.

If you see a multicast session start and then suddenly grind to a halt after a minute or two, the problem is that the switch is timing out the multicast group, because it's not being refreshed. The way the IGMP protocol is designed, hosts send out notices when they join a group (which tends to alert the switch initially) and thereafter, it's up to a device designated as the "IGMP querier" to periodically send out packets to check that hosts are still interested in the multicast traffic. Usually, routers do this job (or the routing modules in high-end switches) but it's important that something is doing it.

Thanks for your answers.
that what my understanding of the problem, that there was something in the switch which helps from connecting both PCs.

the thing is, cheking the 3Com's config is impossible (as far as I know)... I'll try tomorrow to get another one, a manageable switch, dunno where I could get one actually....

I checked the HP Superstack 1100, nothing relevant about the multicast....

The only way I got it to work is by using the server's IP and the session name...

Thanks for your explanations ;)