Ghost Solution Suite

 View Only

"Waiting for Ghostcast session to start".. FIXED.

  • 1.  "Waiting for Ghostcast session to start".. FIXED.

    Posted May 21, 2014 03:44 AM

    Greetings!

    Until recently, we have used Ghost with DOS-based VFD images to inject drivers and get Ghost client to communicate with our Ghostcast server.
    This worked fine, except that finding drivers have started to become a bit troublesome for us, therefore we have stopped using the DOS-based VFD's, installed Windows Deployment Services, and created a custom WinPE 3.0 image to connect Ghost client to the server.

    Now.. This works fine with just one client (Unicast), but when we connect two clients to the same session, Ghost freezes. 
    Clients are stuck with the "Waiting for Ghostcast session to start", even though we have indeed pressed "Send" from the server console.
    I did suspect this to be because of the parameters we use after "ghost32.exe" (-clone,mode=restore,src=@MC3,dst=1 -sure -pfile=Z:\ghost_log -ntexact)
    These are exactly the same parameters that we used before, and they worked. I have tried removing the "-ntexact" parameter also.

     

    I have been successful in starting a multicast session when I start ghost32.exe with only the "-pfile=Z\ghost_log"-parameter set, and manually typing in the session name on two clients. Therefore I have concluded that my NIC and switch are capable of multicasting.

     

    The server is directly connected to a Cisco Catalyst 2960-S, on which the ports in use are configured with the following commands:

    "Duplex full"
    "Speed 1000"
    "Nonegotiate"
    "Switchport mode access"
    "Spanning-tree portfast"

    Back when we used the DOS-based VFD's, we used an unmanaged switch, and multicasting worked back then also.
    We are very confused about this. Any help in getting multicast to work with a preset session name would be much appreciated!

     

    EDIT: The disappointingly simple solution to the problem was to disable firewall inside WinPE. wpeutil disablefirewall fixed our problem.

     

     

     

     

    Regards,
    Vegard Mathisen.