Ghost Solution Suite

 View Only

  • 1.  "Polling for Server" on Multicast - Fine on UniCast

    Posted May 24, 2007 09:47 AM
    Hi all,
     
    I've been practicing with Ghost SS (2.0.1).
     
    If I perform a Multicast session to 1 machine, it will end up (after writing the image) polling for the server.
    If I perform a Unicast session to 1 machine, it will finish correctly.
     
    What am I missing?  This is the same machine and cabling both times...
     
    We haven't yet got decent Layer 3 Managed switches in the rooms, but it strikes me odd that Unicast and Multicast do different things when only 1 machine is in use.
     
    Glad of any advice,
    Chris.


  • 2.  RE: "Polling for Server" on Multicast - Fine on UniCast

    Posted May 24, 2007 07:21 PM
    Hi Chris,
     
    Can you please give us more information about your scenario?
    When you are using multicast:
    1) When in the polling state, is the client acknowledged by the server or is it just polling for the console? If it's just polling for the bound server, the connection with the server is lost.
    2) If you reboot the machine does it go back to DOS (in the polling state) or boot into Windows?
    3) Are there other steps involved in the task?
    4) Does the task finish successfully, with warnings or simply fail? If it fails or there are warnings, can you please indicate the step that is failing or have warnings and post the details of the step? Also, if there is an error file, can you please send it across?
     
    Thank you,
    Adina
     
     


  • 3.  RE: "Polling for Server" on Multicast - Fine on UniCast

    Posted May 25, 2007 08:01 AM

    It writes the image to the HDD fine.  Then: -

    c:\ghost\ghost.exe -clone,dst=1,mode=restore,src=@serverpush -batch -sgb -sgt
    time IP : Port polling for bound server servername
    time IP : Port polling for bound server servername
    time IP : Port polling for bound server servername
    time IP : Port polling for bound server servername
    etc

    On reboot the machine goes back to running PCDos and appears to send an error log but it was very quick and I didn't see.  It then resets again and starts sending status/acknowledge to the server.  Continually.

    It should then run the next step whereby it applies the configuration to the machine so that its domain ready.  However I have run it before with no configuration and it does the same thing.

    I reset once more and again it goes to the status/acknowlegement phase.  On the console at this point it said the clone failed and it was unable to retrieve this ghosterr.txt file.  I have been unable to locate this file on the machine.

    To get out of the loop I pressed Ctrl-C. 


    --
    Task Name: Clone_20070525_122424
    User: Administrator
    Execution Time: 25/05/2007 12:24:25
    Number of client machines: 1
    Clients finished OK: 0

    Task warnings:0

    Task process listing
    IT10 - administrator 00-50-8D-C2-8B-0D Update DOS system files 25/05/2007 12:24:36 Success
    IT10 - administrator 00-50-8D-C2-8B-0D Update DOS Network Drivers 25/05/2007 12:24:36 Success
    IT10 - administrator 00-50-8D-C2-8B-0D Create machine account 25/05/2007 12:24:37 Success
    Details for: Create machine account
    IT10, LDAP://Server02.CURRICULUM//DC=CURRICULUM
    Computers
    IT10 - administrator 00-50-8D-C2-8B-0D Prepare configuration 25/05/2007 12:24:55 Success
    IT10 - administrator 00-50-8D-C2-8B-0D To Virtual Partition 25/05/2007 12:31:49 Success
    IT10 - administrator 00-50-8D-C2-8B-0D Clone 25/05/2007 12:40:53 Failed
    Details for: Clone
    Clone failed and could not open the ghosterr.txt file for retrieval.
    --

    On a Unicast it next goes to Ghost Walker to change the SID.  Then it puts the system back onto the domain.

    Message Edited by CMTout on 05-25-200705:02 AM



  • 4.  RE: "Polling for Server" on Multicast - Fine on UniCast

    Posted May 25, 2007 11:44 AM
    It sounds like ghost didnt actually successfully image the machine correctly, or at least it doesnt think it did.  Is there a ghosterr.txt file at the root or most likely in the ghost folder of the ghostboot partition?


  • 5.  RE: "Polling for Server" on Multicast - Fine on UniCast

    Posted May 28, 2007 12:54 AM
    Hi Chris,
     
    It looks like the client looses the connection with the server after the clone is done and remains in the polling state, trying to get acknowledgement from the console. Not knowing the status of the client, the console considered that the clone failed. It is actually very likely that the clone was successful.
    When you reboot the client, the client goes back to virtual partition and, although this time gets acknowledged by the console, because the clone is considered failed it will remain in virtual partition until you press 'Ctrl-C', which will destroy the VP and boot the client back to Windows.
     
    Still the question remains why it behaves differently in unicast. To help us dig further, can you press 'Ctrl-X' instead of 'Ctrl-C' when in VP and type the command set? Please post what is displayed when this command is run.
    Also, do you run the unicast and the multicast sessions on the same machine or on different machines?
     
    Adina


  • 6.  RE: "Polling for Server" on Multicast - Fine on UniCast

    Posted May 28, 2007 06:40 AM
    Thanks for your advice.
     
    It's half term at the moment, and I'm not employed holidays...  I will be in tomorrow to deal with something else, but I probably won't get chance to play with Ghost.
     
    However, the following Monday is back to normal!  I will try what you suggest and see what happens: -
     
    I did a search on the entire cloned machine and found no ghosterr.txt, I only use a virtual partition (on the fly) and there is no dedicated ghost partition on the cloned machine.
    Yes I use the same machine for both the multicast and unicast test, from the same server.  Only setting different in the task is that its either Multi or Uni cast.
     
    You are correct with that the clone is successful, all data is correctly written to the computer.  It just fails to go to the next step and either change SID or re-add to the domain if run as multicast.


  • 7.  RE: "Polling for Server" on Multicast - Fine on UniCast

    Posted Jun 05, 2007 04:56 AM
    Hi again,
     
    I've tried what you said and this is what I get with set: -
     
    COMSPEC=C:\COMMAND.COM
    PROMPT=Type ghreboot to attempt to return to Windows $_$P$G
    PATH=c:\ghost;\ghost;c:;\
     
    I also retrieved the NETLOG.txt file from the machine: -
     
    Log Level Debug
       619736 WATTCP: <IP> = <10.2.88.66>
              Set IP address to 0xa025842
              WATTCP: <NETMASK> = <255.255.252.0>
              Set subnet to 0xfffffc00
              WATTCP: <GATEWAY> = <10.2.88.16>
              Set default gateway to 0xa025810
              Set packet driver receive mode to 4
              _ip_share_mode = 0
       619754 UDP socket buffer initialised to 10 packets
              UDP Packets Dropped: 0
              UDP socket buffer initialised to 10 packets
       619756 UDP socket buffer initialised to 10 packets
              UDP Packets Dropped: 0
       619793 DHCP Lease exported
       619794 UDP Packets Dropped: 0
              Fragments dropped (Too Large): 0
              Fragments dropped (No Space) : 0
              Fragments dropped (Timed Out): 0

              Packet Driver Packets Dropped: 0
              Packet Driver Statistics
              Packets In   0
              Packets Out  0
              Bytes In     0
              Bytes Out    0
              Errors In    0
              Errors Out   0
              Packets Lost 0
       632243 WATTCP: <IP> = <10.2.88.66>
              Set IP address to 0xa025842
              WATTCP: <NETMASK> = <255.255.252.0>
              Set subnet to 0xfffffc00
              WATTCP: <GATEWAY> = <10.2.88.16>
              Set default gateway to 0xa025810
              Set packet driver receive mode to 4
              _ip_share_mode = 0
       632261 UDP socket buffer initialised to 10 packets
       632646 UDP socket buffer initialised to 10 packets
       632826 UDP Packets Dropped: 0
       633046 UDP socket buffer initialised to 10 packets
       633226 UDP Packets Dropped: 0
       633846 UDP socket buffer initialised to 10 packets
       634026 UDP Packets Dropped: 0
       634726 UDP Packets Dropped: 0
              Fragments dropped (Too Large): 0
              Fragments dropped (No Space) : 0
              Fragments dropped (Timed Out): 0

              Packet Driver Packets Dropped: 0
              Packet Driver Statistics
              Packets In   0
              Packets Out  0
              Bytes In     0
              Bytes Out    0
              Errors In    0
              Errors Out   0
              Packets Lost 0
     
     
    --
     
    I also told the console to make a log... However it came out at over 300mb so I doubt I can zip that to anything reasonable!  If not I will have to re-do the clone with a less "verbose" log option.