Ghost Solution Suite

 View Only
  • 1.  Unable to connect to session

    Posted Mar 13, 2007 05:46 PM
    I am attempting to use GhostCast Server v8.3 to pull an image from a computer in order to test a new isolated network. I am concerned that there is some port that is blocked that needs to be opened. I turned on the logging option and the only difference I see between a successful and unsuccessful session is the following line at the end of the log file:

    R: LEN: <277> SESSION: <lah123> FROM: <10.222.132.12:1025>
    S: LEN: <260> SESSION: <lah123> TO: <10.222.132.12:1025>

    In a session where I get the 10030 error, the above lines are repeated several times. Port 1025 is open. Could there be another reason why I am seeing this?


  • 2.  RE: Unable to connect to session

    Posted Mar 13, 2007 07:22 PM
    Hi Linda,

    Error 10030 indicates that there is no connectivity between ghostcast server and ghost.

    I believe ghost uses multicast to discover a ghostcast server session.
    Ghost will send out a UDP packet to multicast address 224.77.0.0 on port 6666 for the initial discovery. Ghostcast server should then reply using port 6666.

    Not sure how your isolated network is set up, but maybe you need to open port 6666?

    Hope that helps

    Cheers

    Chris


  • 3.  RE: Unable to connect to session

    Posted Mar 14, 2007 10:50 AM
    From the logs that are created it is usin the following address for multicast:

    Server multicast address set to 224.77.58.44

    Should it be set explicitly to 244.77.0.0?

    Other parts of the log file seem to indicate port 6666 is open:
    Bound RML socket to 0.0.0.0:4607
    Setting multicast scope to 16
    State was 0, now 1
    Bound TCP socket to 0.0.0.0:4608
    Bound UDP socket to 0.0.0.0:6666


  • 4.  RE: Unable to connect to session

    Posted Mar 14, 2007 10:26 PM
    The 244.77.0.0 group is used from the client to the server, to find the server (or rather, the session). All the image servers listen to this, and respond to requests that are for them specifically.

    For the actual work of sending a multicast session, the server picks a random multicast address in the 224.77.x.x range and tells the clients that they should join that group and listen to it. The server-side log is telling you about the random address chosen for the session.

    Once the transfer phase begins, the server sends to the clients on that address, which they have then subscribed to (thus telling the intermediate switches and routers how to optimise the traffic flow).

    > Other parts of the log file seem to indicate port 6666 is open:

    Well, they are telling you that the server is trying to do something with that port.

    Whether it is actually open or not is something our software can't tell - if a firewall is blocking incoming or outgoing data on a port, the application program trying to send/receive data has no way of discovering this fact.



  • 5.  RE: Unable to connect to session

    Posted Jul 11, 2007 11:39 AM
    I hope this help anyone with this problem!
    To Multicast on a Windows 2003 Server you will have to enable Reliable Multicast Protocol on your server:
    ·Right Click on My Network Places, click on Properties
    ·Right click on your Local Area Connection & click on Properties
    ·Click on the Install Button
    ·Double Click on Protocol
    ·Click on Reliable Multicast Protocol & click OK
    ·Click Close to save the changes

    How to Push an Image to a Client w/o an Operating System
    To create the bootable floppy disk: (will need 2 floppy disks)
    ·Click Start; All Programs; Symantec Ghost; Ghost Boot Wizard
    ·In the Symantec Ghost Boot Wizard window, select Network Boot Package, and then click Next
    ·Choose correct NDIS2 Driver & Click Next
    ·In the DOS Version window, select Use PC-DOS, and then click Next
    ·In the Client Type window, verify that the path to Ghost.exe is correct, click Next
    ·In the Client Type window, verify that the path to C:\Program Files\Symantec\Ghost\ghost.exe is correct, click Next
    ·In the External storage support window, click Next
    ·In the Network settings window, click on DHCP will assign the IP settings Next
    ·Insert the first floppy disk into the Ghost Server disk drive, and then click Next
    ·In the Review window, verify the information you selected, and then click Next
    ·In the Format window, verify the settings, and then click Start
    ·Click OK when the Format complete screen appears & click Close when the Format window reappears. Ghost will
    copy the necessary boot files to the first floppy disk
    ·You will be prompted to insert the second disk
    ·Click OK when the Format complete screen appears & click Close when the Format window reappears. Ghost will
    copy the necessary boot files to the second floppy disk
    ·Click OK after inserting the second disk & name the first disk; “Disk 1 with driver name & computer type”
    ·Click Finish & remove second floppy & name it Disk 2 with driver name & computer type

    Push Image File to Client:
    ·Insert disk 1 floppy into A: drive on client computer
    **If you receive below errors after inserting floppy disk 1:
    -LTE0016E:  Driver name missing in Protocol.ini
    -Error: 33 Unable to bind

    ·Insert disk 2 floppy into A: drive of client computer
    **If you receive below error after inserting floppy disk 2:
     
    -The Symantec Ghost 11.0.1 gray ghost window comes up but
    the multicast and peer to peer buttons are grayed out
     
    **You are either using the wrong NDIS driver or you need to:
     
    -If possible=check to see which slot location (number) your NIC is in
    by clicking on the properties of the NIC and view the location. If the
    slot number is different in the protocol.ini file change it to the correct slot location & resave your protocol.ini file.
     
    -If you can’t check the slot location=keep changing the number in the
    protocol.ini file, remake NDIS driver floppy disks & retry them in
    your client computer until your file BINDS!!!!!!
     
    **If you have multiple clients to image:
     
    -Make copies of both disks, insert disk 1 into A: drive of the Ghost Server or your desktop computer, open A:\ghost & right click on the wattcp file & open with notepad and give each set of disk 1 a different host address (192.168.16.22) & save. Best practice: to print the whole IP address onto each disk set
     
    ·On the Ghost Server:  Double click on the GhostCast Server icon
    ·Enter a Session Name
    ·Browse to image file you wish to push
    ·Click on Client Count button
    ·Click on More Options button
    ·Click on Client count and type in amount of clients your pushing too
    ·Click on Accept Clients
    ·On the Client Computer:  Click on GhostCast
    ·Click on Multicast
    ·Type in name of session  you chose on the GhostCast Server
    ·Click on OK three times & then click on Yes
    ·When the session is complete remove the floppy from the A drive
    ·Click on reset computer