Ghost Solution Suite

 View Only
  • 1.  GhostCode 19932 - Failed to connect to GhostCast Server

    Posted Apr 28, 2011 06:12 AM

    When ghosting from a windows 7 pc, I keep getting this error: "Failed to connect to GhostCast server with GhostCode 19932". It gets stuck at 'Establishing TCP connection...'.

    Apparently, this has something to do with the firewall. Though, when I ghost with xp, nothing goes wrong. McAffee is turned off and all the correct ports are open:

    Destination ports:

    UDP 6666 - 6669
    TCP 1024 - 4999
    TCP/UDP 137 - 139, 445

    Source ports:
    UDP 7777
    TCP/UDP 1345 - 1347

    What can I do? I've already ran live-update until I'm at version 11.5.1.2266 even though live-update gave an error and said that update was interrupted. Now when I run live-update it says everything is up to date.

    Output of GHOSTERR.TXT:

    *********************************
    Date   : Thu Apr 28 11:57:31 2011
    Error Number: (504)
    Message: Failed to connect to GhostCast server with GhostCode 19932

    Version: 11.0.0.1502 (Dec  4 2006, Build=1502)
    OS Version: DOS v7.10
    Command line arguments: -sure -rb -clone,mode=prestore,SRC=@mchp8000,dst=2:1
    Active Switches :
           AutoName
    PathName            :
    DumpFile            :
    DumpPos             : 0
    FlagImplode         : 0
    FlagExplode         : 0

    CloneSrc            : @MCHP8000
    BatchPartSrc        : 0
    BatchPartMSrc       :

    CloneDst            : 2:1
    BatchPartDst        : 0

    Operation Details :
      Total size.........0
      MB copied..........0
      MB remaining.......0
      Percent complete...0%
      Speed..............0 MB/min
      Time elapsed.......0:00  
      Time remaining.....0:00  

    Program Call Stack
    AbortLog
    Generic_Abort
    MCastAbort
    OpenTCP
    MCastRemoteComm::connectMaster
    Connect
    CheckCloneSwitches
    ProcessArgumentsToPass
    sub_main
    main

    Call Stack
      0x0039623c
      0x0009cbd1
      0x0009c40c
      0x0009bae7
      0x0009d6b2
      0x0003c52f
      0x0003c6ee
      0x000b73a4
      0x0008d63f
      0x00028ae0
      0x0002c1a9
      0x00030c54
      0x00030dd5
      0x00004ad8
      0x00003f2f
      0x0039f468
    End Call Stack


    Start heap available: 1034420224
    Cur   heap available: 1034158080
    Total Memory:         1041891328

    Allocated
       1024 DpmiDjgpp.cpp:56
      33504 ghost.cpp:1394
         64 DiskDriveAccessExInt13.cpp:139
         48 DiskDriveAccessExInt13.cpp:139
        528 IdeDmaServerPci.cpp:127
        528 IdeDmaServerPci.cpp:127
        528 IdeDmaServerPci.cpp:127
        528 IdeDmaServerPci.cpp:127
        528 IdeDmaServerPci.cpp:127
        528 IdeDmaServerPci.cpp:127
    Free
         80 DiskDriveAccessExInt13.cpp:102
        512 DiskDriveAccessInt13.cpp:184
       1024 DiskDriveAccessInt13.cpp:184
       2048 DiskDriveAccessInt13.cpp:184
      32768 BlockDeviceDosDrive.cpp:392

    Fat details:

    NTFS details:
    ----------------

    NTFS Global Flags:
    ----------------
      contiguousWrite=1 forceDiskClusterMapping=0
      inhibitCHKDSK=1 ignoreBadLog=0 ignoreCHKDSKBit=0
      enable_cache=0 xfrbuflen=0
      last_attr_type = 0
      loadExact = 0
    ----------------

    Disk Info :
      remote.............0
      drive..............0
      sectorsUsedCount.......0
      estimatedUsedCount.....0
      numPartitions..............0
      Version............0

     # Ord Boot Id Ext     First        Num       Last       Used NTFS

    Disk Info :
      remote.............0
      drive..............0
      sectorsUsedCount.......0
      estimatedUsedCount.....0
      numPartitions..............0
      Version............0

     # Ord Boot Id Ext     First        Num       Last       Used NTFS

    Fixed Drives

    Drive 128
    Int 13h (Active)
    Total Sectors            15694812
    Bytes per Sector         512
    MB                       7663
    Cylinders                1021
    Heads                    244
    Sectors per Track        63
    Successful IO Count      89

    Extended Int 13h
    Total Sectors            15695871
    Bytes per Sector         512
    MB                       7663
    Successful IO Count      0

    Drive 129 SAMSUNG HD161HJ S14JJ9AQA14697
    Int 13h
    Total Sectors            16450560
    Bytes per Sector         512
    MB                       8032
    Cylinders                1024
    Heads                    255
    Sectors per Track        63
    Successful IO Count      0

    Extended Int 13h
    Total Sectors            312581808
    Bytes per Sector         512
    MB                       152627
    Successful IO Count      0

    IDE using PIO
    Total Sectors            312581808
    Bytes per Sector         512
    MB                       152627
    Cylinders                16383
    Heads                    16
    Sectors per Track        63
    Successful IO Count      0

    IDE using UDMA (Active)
    Total Sectors            312581808
    Bytes per Sector         512
    MB                       152627
    Cylinders                16383
    Heads                    16
    Sectors per Track        63
    Successful IO Count      47

    Floppy Drives

    Remote Drives
    AsyncIo : 0
    ConvMemoryAllocationFactoryDpmi diagnostic...
    =============================================

    Conventional Memory
    Initial Conventional Memory Size = 389104
    Current Conventional Memory Size = 248832

    Allocated
       1024 DpmiDjgpp.cpp:56
      33504 ghost.cpp:1394
         64 DiskDriveAccessExInt13.cpp:139
         48 DiskDriveAccessExInt13.cpp:139
        528 IdeDmaServerPci.cpp:127
        528 IdeDmaServerPci.cpp:127
        528 IdeDmaServerPci.cpp:127
        528 IdeDmaServerPci.cpp:127
        528 IdeDmaServerPci.cpp:127
        528 IdeDmaServerPci.cpp:127
    Free
         80 DiskDriveAccessExInt13.cpp:102
        512 DiskDriveAccessInt13.cpp:184
       1024 DiskDriveAccessInt13.cpp:184
       2048 DiskDriveAccessInt13.cpp:184
      32768 BlockDeviceDosDrive.cpp:392


    DiskManager diagnostic...
    =========================

    Fixed Drives

    Drive 128
    Int 13h (Active)
    Total Sectors            15694812
    Bytes per Sector         512
    MB                       7663
    Cylinders                1021
    Heads                    244
    Sectors per Track        63
    Successful IO Count      89

    Extended Int 13h
    Total Sectors            15695871
    Bytes per Sector         512
    MB                       7663
    Successful IO Count      0

    Drive 129 SAMSUNG HD161HJ S14JJ9AQA14697
    Int 13h
    Total Sectors            16450560
    Bytes per Sector         512
    MB                       8032
    Cylinders                1024
    Heads                    255
    Sectors per Track        63
    Successful IO Count      0

    Extended Int 13h
    Total Sectors            312581808
    Bytes per Sector         512
    MB                       152627
    Successful IO Count      0

    IDE using PIO
    Total Sectors            312581808
    Bytes per Sector         512
    MB                       152627
    Cylinders                16383
    Heads                    16
    Sectors per Track        63
    Successful IO Count      0

    IDE using UDMA (Active)
    Total Sectors            312581808
    Bytes per Sector         512
    MB                       152627
    Cylinders                16383
    Heads                    16
    Sectors per Track        63
    Successful IO Count      47

    Floppy Drives

    The following devices do not use an IRQ:
       (0x00, 0x00, 0x00):   IRQ: 0x00, INT#: -, Link: 0x00
          Class: Bridge, SubClass: Host/PCI
          Vendor: 0x8086, Device: 0x29b0
       (0x00, 0x1c, 0x00):   IRQ: 0xff, INT#: -, Link: 0x00
          Class: Bridge, SubClass: PCI/PCI
          Vendor: 0x8086, Device: 0x2940, RoutePINS: 0x68, 0x69, 0x6a, 0x6b,
       (0x00, 0x1e, 0x00):   IRQ: 0xff, INT#: -, Link: 0x00
          Class: Bridge, SubClass: Sub Decode PCI/PCI
          Vendor: 0x8086, Device: 0x244e
       (0x00, 0x1f, 0x00):   IRQ: 0x00, INT#: -, Link: 0x00
          Class: Bridge, SubClass: PCI/ISA
          Vendor: 0x8086, Device: 0x2914, RoutePINS: 0x61, 0x62, 0x62, 0x00,
    The following hard wire-ord devices share IRQ 5:
       (0x00, 0x02, 0x00):   IRQ: 0x05, INT#: A, Link: 0x60
          Class: Display, SubClass: VGA compatible
          Vendor: 0x8086, Device: 0x29b2, RoutePINS: 0x60, 0x61, 0x00, 0x00,
       (0x00, 0x03, 0x00):   IRQ: 0x05, INT#: A, Link: 0x60
          Class: Simple Com, SubClass: Other Com
          Vendor: 0x8086, Device: 0x29b4, RoutePINS: 0x60, 0x61, 0x62, 0x00,
    The following hard wire-ord devices share IRQ 11:
       (0x00, 0x03, 0x03):   IRQ: 0x0b, INT#: B, Link: 0x61
          Class: Simple Com, SubClass: Serial 16550-comp
          Vendor: 0x8086, Device: 0x29b7, RoutePINS: 0x60, 0x61, 0x62, 0x00,
    The following hard wire-ord devices share IRQ 10:
       (0x00, 0x03, 0x02):   IRQ: 0x0a, INT#: C, Link: 0x62
          Class: Mass Storage, SubClass: IDE Controller
          Vendor: 0x8086, Device: 0x29b6, RoutePINS: 0x60, 0x61, 0x62, 0x00,
       (0x00, 0x1f, 0x02):   IRQ: 0x0a, INT#: B, Link: 0x62
          Class: Mass Storage, SubClass: IDE Controller
          Vendor: 0x8086, Device: 0x2920, RoutePINS: 0x61, 0x62, 0x62, 0x00,
       (0x00, 0x1f, 0x05):   IRQ: 0x0a, INT#: B, Link: 0x62
          Class: Mass Storage, SubClass: IDE Controller
          Vendor: 0x8086, Device: 0x2926, RoutePINS: 0x61, 0x62, 0x62, 0x00,
    The following hard wire-ord devices share IRQ 5:
       (0x00, 0x19, 0x00):   IRQ: 0x05, INT#: B, Link: 0x63
          Class: Network, SubClass: Ethernet
          Vendor: 0x8086, Device: 0x10bd, RoutePINS: 0x63, 0x63, 0x00, 0x00,
    The following hard wire-ord devices share IRQ 10:
       (0x00, 0x1a, 0x00):   IRQ: 0x0a, INT#: A, Link: 0x68
          Class: Serial Bus, SubClass: USB UHCI
          Vendor: 0x8086, Device: 0x2937, RoutePINS: 0x68, 0x69, 0x6a, 0x00,
       (0x00, 0x1d, 0x00):   IRQ: 0x0a, INT#: A, Link: 0x68
          Class: Serial Bus, SubClass: USB UHCI
          Vendor: 0x8086, Device: 0x2934, RoutePINS: 0x68, 0x69, 0x6a, 0x00,
       (0x00, 0x1d, 0x07):   IRQ: 0x0a, INT#: A, Link: 0x68
          Class: Serial Bus, SubClass: USB EHCI
          Vendor: 0x8086, Device: 0x293a, RoutePINS: 0x68, 0x69, 0x6a, 0x00,
    The following hard wire-ord devices share IRQ 11:
       (0x00, 0x1a, 0x01):   IRQ: 0x0b, INT#: B, Link: 0x69
          Class: Serial Bus, SubClass: USB UHCI
          Vendor: 0x8086, Device: 0x2938, RoutePINS: 0x68, 0x69, 0x6a, 0x00,
       (0x00, 0x1b, 0x00):   IRQ: 0x0b, INT#: A, Link: 0x69
          Class: Multimedia, SubClass: Unknown Multimedia
          Vendor: 0x8086, Device: 0x293e, RoutePINS: 0x69, 0x00, 0x00, 0x00,
       (0x00, 0x1c, 0x01):   IRQ: 0x0b, INT#: B, Link: 0x69
          Class: Bridge, SubClass: PCI/PCI
          Vendor: 0x8086, Device: 0x2942, RoutePINS: 0x68, 0x69, 0x6a, 0x6b,
       (0x00, 0x1d, 0x01):   IRQ: 0x0b, INT#: B, Link: 0x69
          Class: Serial Bus, SubClass: USB UHCI
          Vendor: 0x8086, Device: 0x2935, RoutePINS: 0x68, 0x69, 0x6a, 0x00,
    The following hard wire-ord devices share IRQ 5:
       (0x00, 0x1a, 0x02):   IRQ: 0x05, INT#: C, Link: 0x6a
          Class: Serial Bus, SubClass: USB UHCI
          Vendor: 0x8086, Device: 0x2939, RoutePINS: 0x68, 0x69, 0x6a, 0x00,
       (0x00, 0x1a, 0x07):   IRQ: 0x05, INT#: C, Link: 0x6a
          Class: Serial Bus, SubClass: USB EHCI
          Vendor: 0x8086, Device: 0x293c, RoutePINS: 0x68, 0x69, 0x6a, 0x00,

     

    FilesystemManager diagnostic...
    ===============================

    Volume 1
    VolumePos: 1.1:
    DriveLetter: C:
    Description:    6.83GB Primary Disk 0 Offset   31.50KB    6.83GB
    Type:        fsfFat32
    Name:        DOS

    Volume 2
    VolumePos: 1.2:
    DriveLetter: D:
    Description:  668.02MB Primary Disk 0 Offset    6.83GB  668.02MB
    Type:        fsfFat32
    Name:        WIN7PE

    Volume 3
    VolumePos: 2.1:
    DriveLetter:
    Description:   19.53GB Primary Disk 1 Offset   31.50KB   19.53GB SAMSUNG HD161HJ S14JJ9AQA14697
    Type:        fsfNtfsWindowsXP
    Name:       

    Volume 4
    VolumePos: 2.2:
    DriveLetter:
    Description:  129.52GB Primary Disk 1 Offset   19.53GB  129.52GB SAMSUNG HD161HJ S14JJ9AQA14697
    Type:        fsfNtfsWindowsXP
    Name:       


    FilesystemMounter diagnostic...
    ===============================


    LfoFilesystemManager diagnostic...
    ==================================

    Filesystem Index: 0
    Filesystem Descriptor:
      ID's:
        ID Type: 2
        ID: C:
        ID Type: 1
        ID: 1.1:
        ID Type: 4
        ID: DOS:
      DriveType: 4
      FilesystemInfo:
        formatType: 3
        volumeName: DOS

    Filesystem Index: 1
    Filesystem Descriptor:
      ID's:
        ID Type: 2
        ID: D:
        ID Type: 1
        ID: 1.2:
        ID Type: 4
        ID: WIN7PE:
      DriveType: 4
      FilesystemInfo:
        formatType: 3
        volumeName: WIN7PE

    Filesystem Index: 2
    Filesystem Descriptor:
      ID's:
        ID Type: 1
        ID: 2.1:
      DriveType: 4
      FilesystemInfo:
        formatType: 8
        volumeName:

    Filesystem Index: 3
    Filesystem Descriptor:
      ID's:
        ID Type: 1
        ID: 2.2:
      DriveType: 4
      FilesystemInfo:
        formatType: 8
        volumeName:


    *********************************



  • 2.  RE: GhostCode 19932 - Failed to connect to GhostCast Server

    Posted Apr 28, 2011 06:54 AM

    Can I suggest you type 19932 into the search engine and have a look at some previous postings about this error - some have the solution flag checked so the threads did identify causes.

    The items to check are that you have VISTA 32 bit drivers added to WinPE for your NIC, as the version of WinPE used in GSS 2.5 is based on the Vista kernel. An incorrect driver may be preventing a network connection being established.

    The other common issue involves the ability of any switches in your network to handle multicast /IGMP traffic. In one previous thread, the network guys had changed the switch settings and stopped Ghost working.

    If your target system has SATA drives, check that WinPE is able to access the drives as you may also need to add a SATA driver if the chipset on your machine is not natively supported by WinPE 2.0



  • 3.  RE: GhostCode 19932 - Failed to connect to GhostCast Server

    Posted Apr 28, 2011 10:28 AM

    Not sure that it is related to version or not but you look to be using version 11.0 and this was out prior to windows 7.  There is a new version 11.5 build 2266 that has windows 7 support.   I hadn't tried 11.0 on win 7 to know if it works or not but I know it isn't supported.    As for the drivers upgradeing is important but you may find dos drivers are harder and harder to find.    Ed is talking about vista drivers for the ghost boot disk that runs Windows PE.   

    Windows PE can deal with modern hardware more efficiently than Dos ever could so that alone would be worth the upgrade to the latest version of ghost.

    From your log file.
    Version: 11.0.0.1502 (Dec  4 2006, Build=1502)
    OS Version: DOS v7.10
     

    cheers.



  • 4.  RE: GhostCode 19932 - Failed to connect to GhostCast Server

    Posted Apr 28, 2011 10:44 AM

    Well spotted - there appears to be a discrepancy between the version recorded in the logfile (11.0.0.1502 ) and the version the O/P believes that LiveUpdate has applied (11.5.1.2266).

    Unless I am mistaken, I was under the impression that versions 11.0 and 11.5 were separate products with separate LiveUpdate channels, and that an upgrade needed to be purchased to get from 11.0 to 11.5.

    You can of course download the eval of 11.5 and see whether that works before going down the upgrade path.



  • 5.  RE: GhostCode 19932 - Failed to connect to GhostCast Server

    Posted Apr 28, 2011 12:14 PM

    ha ha Ed I missed the part where he said he was up to 11.5.   I was focused ont he output file and missed that.  Sorry for waisting time talking about the praises of upgradeing to 11.5   

       What we have here is a case of an old boot disk not connecting to a new server.    Label that disk 11.0 or toss it so it can't be confused again and then make a new on.   That is what I would bet my lunch money on.   



  • 6.  RE: GhostCode 19932 - Failed to connect to GhostCast Server
    Best Answer

    Posted May 12, 2011 08:23 AM

    Thanks for the replies so far. It appears that it is a port-related problem.

    At this workspot, we are behind the firewall of the university. When I put the ghostcast computer in a separate vlan with the ports named in the first post, it stalls at 'Establishing TCP connection'.

    However, when the ICT department opens all ports on that particular vlan, ghosting works fine. Therefore, my question: Does Ghost need other ports to be opened on windows 7 than the ports below?

    Destination ports;
    UDP 6666 - 6669
    TCP 1024 - 4999
    TCP/UDP 137 - 139, 445
    Source ports;
    UDP 7777
    TCP/UDP 1345 - 1347
     

    Thanks in advance

    Edit: It worked with all ports open and the firewall + mcaffee off. Now trying to see if it works when firewall and mcaffee in normal/default config but still with all the ports open.

    Edit 2: Additional ports need to be opened. I got these from the GhostCast Server log. My working settings:

    Destination ports:
    UDP 6666 - 6669
    TCP 1024 - 4999, 49172
    TCP/UDP 137 - 139, 445, 63552

    Source ports:
    UDP 7777
    TCP/UDP 1345 - 1347, 63552