Questions

Symantec Ghost 7.0 Won't Multicast Anymore = Times Out

+
0 Votes
Locked

Symantec Ghost 7.0 Won't Multicast Anymore = Times Out

link470
Hello,

I've been using Symantec Ghost 7.0 for quite some time now at work. We use the multicasting feature so we can have a computer with the images on it in the server room and then go onto computers around the network with a boot floppy and have the same session ID on both, then send the image to each machine at once. You know the drill if you're a Symantec Ghost user.

But starting this morning, I go to image a machine, and it won't image. They're all compaq evo's in this department and are using the same book disk. I tried making other disks, and that didn't help. I tried another port on the network and that didn't help, I even tried plugging directly into the same switch as the multicast server and that doesn't even help. Tried other evo's as well.

What's happening, is that the multicast session starts fine [the server sees it in the list and I'm able to start the multicast] and then after 50 to 100MB's copied, it times out and stops. Ghostcode 19922. [AKA "Error Code", but Symantec is "special"]. Anyway, this is completely random and I have a ton of machines I need to image. If anyone else has come across this I would greatly appreciate any advice. I'm just confused because it worked perfectly a week ago and now it's not, and permissions aren't an issue because it's able to copy the 50 to 100MB's without a problem before it dies. Just thinking out loud:) Thanks!
  • +
    0 Votes
    sgt_shultz

    i am just thinking out loud also but if nothing else has changed maybe it is a network traffic problem or a bad nic in the server (power save mode??) or a badly fragmented drive there...when i try to solve stuff like this i sometimes try to just get it working any way i can think of then figure out 'backwards' what happened. so what i am getting at is have you considered putting the image on an external drive and hiking it right to the client to see if it'll work that way

    +
    0 Votes
    sgt_shultz

    you sure nobody group policy'd the firewall up on your clients. or elsewhere. did you see this symantec article
    Document URL: http://entsupport.symantec.com/docs/n2005101310401325

    Error 19922 or multicast stops responding when multicasting with Ghost32 in Windows PE

    +
    0 Votes
    Desktop Veteran

    The big question is: What changed? Be aware of the fact that the ability to use multicasting is dependent on the routers and switches on your network having the "multicasting" feature/ability turned on.

    I ran into the same issue when we rearranged our setup room. Without really thinking of it, I moved the network patch cable, which in turn changed the port on the switch in the closet that I was using and guess what...the ports on the switch were configured differently.

    Retrace your steps, or ask your network department if they changed anything in the closet, or on any of the switches. Something changed.

    This feature is built into the application, it will use it when you choose, if the network will allow it. What I mean to say is that it's controlled by the network, not the software. (It's been a long day)

    +
    0 Votes

    Hmm

    link470

    Come to think of it the wiring guys have been around this place all week. Configuring a new classroom to be on the network. I don't understand though why it's able to connect, and then after 50 to 100MB of transfer it stops, shouldn't that initial data not even pass through if the connection isn't allowed?

    +
    0 Votes
    Desktop Veteran

    Your right, that part of it wouldn't make any sense. On the other hand, however, there have been a lot of things with Symantec software over the years that don't make any sense (just my opinion from my experince of course).

    So for the sake of clarity, you start one Ghost Server session, and then boot several PCs up and have them connect to that same session, and once all of them have connected the session starts transferring data...does that sound about right?

    So I read through your initial post again for details I may have missed and it ocurred to me that your description of your scenario suggests that you might be crossing subnets with some of the machines. If you are, the Ghost Cast Server doesn't do real well with that. Transfer rates were horrible, and in some cases the connection could be dropped because too much time passed between packets. So make a note of the transfer rates.

    If you haven't already resolved this issue, watch the client when you connect to the session. If Ghost can't run in Multicast mode it will identify the connection as Unicast (this is what got my attention in my situation). These settings can be overruled, but that doesn't mean it will work.

    From the testing we did even with the Ghost server and all of the clients connected to the same switch, the Unicast sessions got better transfer rates than the Multicast sessions. In fact, when we reimaged 16 PCs in our training lab, I did 8 with individual Unicast sessions, my co-worker did 8 in a Multicast session. We ended up waiting for an extra 1/2 hour for the Multicast session to finish after mine were done.

    There is another benefit to Unicast. With Multicast ALL of the machines have to connect before ANY of them start receiving the image. But with Unicast you can start multiple sessions with different names (ghost1, ghost2, etc) and when the client connects, it starts imaging. And, as I mentioned, the single sessions seem to have faster transfer rates than the multi-sessions.

    I would be curious to know how this all works out for you.

    Good luck.

    +
    0 Votes
    jbracey

    we recently upgraded our network to catalyst 3750 stacked switches. after the upgrade ghost multicast sessions aren't working, same symptoms as described but no errors in the ghost log that I can see. we moved the server into a lab and we ran tests yesterday making sure all the test machines were connected to the same switch stack and in the same vlan. I dialed the ports down to 10/half, removed port-security, removed the broadcast storm control, all attempts to multicast still failed. Cisco has been no help with this so far. has there been any further info on this with you all?

    +
    0 Votes
    IC-IT

    multitasking on the switches. It is disabled by default.

  • +
    0 Votes
    sgt_shultz

    i am just thinking out loud also but if nothing else has changed maybe it is a network traffic problem or a bad nic in the server (power save mode??) or a badly fragmented drive there...when i try to solve stuff like this i sometimes try to just get it working any way i can think of then figure out 'backwards' what happened. so what i am getting at is have you considered putting the image on an external drive and hiking it right to the client to see if it'll work that way

    +
    0 Votes
    sgt_shultz

    you sure nobody group policy'd the firewall up on your clients. or elsewhere. did you see this symantec article
    Document URL: http://entsupport.symantec.com/docs/n2005101310401325

    Error 19922 or multicast stops responding when multicasting with Ghost32 in Windows PE

    +
    0 Votes
    Desktop Veteran

    The big question is: What changed? Be aware of the fact that the ability to use multicasting is dependent on the routers and switches on your network having the "multicasting" feature/ability turned on.

    I ran into the same issue when we rearranged our setup room. Without really thinking of it, I moved the network patch cable, which in turn changed the port on the switch in the closet that I was using and guess what...the ports on the switch were configured differently.

    Retrace your steps, or ask your network department if they changed anything in the closet, or on any of the switches. Something changed.

    This feature is built into the application, it will use it when you choose, if the network will allow it. What I mean to say is that it's controlled by the network, not the software. (It's been a long day)

    +
    0 Votes

    Hmm

    link470

    Come to think of it the wiring guys have been around this place all week. Configuring a new classroom to be on the network. I don't understand though why it's able to connect, and then after 50 to 100MB of transfer it stops, shouldn't that initial data not even pass through if the connection isn't allowed?

    +
    0 Votes
    Desktop Veteran

    Your right, that part of it wouldn't make any sense. On the other hand, however, there have been a lot of things with Symantec software over the years that don't make any sense (just my opinion from my experince of course).

    So for the sake of clarity, you start one Ghost Server session, and then boot several PCs up and have them connect to that same session, and once all of them have connected the session starts transferring data...does that sound about right?

    So I read through your initial post again for details I may have missed and it ocurred to me that your description of your scenario suggests that you might be crossing subnets with some of the machines. If you are, the Ghost Cast Server doesn't do real well with that. Transfer rates were horrible, and in some cases the connection could be dropped because too much time passed between packets. So make a note of the transfer rates.

    If you haven't already resolved this issue, watch the client when you connect to the session. If Ghost can't run in Multicast mode it will identify the connection as Unicast (this is what got my attention in my situation). These settings can be overruled, but that doesn't mean it will work.

    From the testing we did even with the Ghost server and all of the clients connected to the same switch, the Unicast sessions got better transfer rates than the Multicast sessions. In fact, when we reimaged 16 PCs in our training lab, I did 8 with individual Unicast sessions, my co-worker did 8 in a Multicast session. We ended up waiting for an extra 1/2 hour for the Multicast session to finish after mine were done.

    There is another benefit to Unicast. With Multicast ALL of the machines have to connect before ANY of them start receiving the image. But with Unicast you can start multiple sessions with different names (ghost1, ghost2, etc) and when the client connects, it starts imaging. And, as I mentioned, the single sessions seem to have faster transfer rates than the multi-sessions.

    I would be curious to know how this all works out for you.

    Good luck.

    +
    0 Votes
    jbracey

    we recently upgraded our network to catalyst 3750 stacked switches. after the upgrade ghost multicast sessions aren't working, same symptoms as described but no errors in the ghost log that I can see. we moved the server into a lab and we ran tests yesterday making sure all the test machines were connected to the same switch stack and in the same vlan. I dialed the ports down to 10/half, removed port-security, removed the broadcast storm control, all attempts to multicast still failed. Cisco has been no help with this so far. has there been any further info on this with you all?

    +
    0 Votes
    IC-IT

    multitasking on the switches. It is disabled by default.