Ghost Solution Suite

Hi first post first time GSS user. running version 11.0.0.1502

I've used ghost before first time trying there suite. I downloaded the trial and trying to decide if this is something our company wants to invest in.

I've gone through all the tutorials and am trying to just create a basic image. I've got the ghost console up and running no problem. I've remotely installed the client to the computer I would like to create an image from. I start the task and after a few minutes it fails and I can view the event log and see the following steps:

Update DOS system files Success
Update DOS Network Drivers Success
To Virtual Partition Success
Clone Failed

It then instructs me to view the error file which I do and says this

*********************************
Date : Mon Feb 12 10:11:18 2007
Error Number: (10030)
Message: Unable to establish contact with session <ASIITPULL13>.
Check that the GhostCasting Server application is ready
to accept clients!
Version: 11.0.0.1502 Trial (Dec 4 2006, Build=1502)
OS Version: DOS v7.10
Command line arguments: -Z1 -clone,src=1,mode=create,dst=@MCASIITpull13 -batch -igb -sgt

I've repeated this several times and Im watching the ghostcast server waiting to accept clients and none never connect, although the computer i'm trying to image starts the imaging process reboots to what appears to be the virtual partition and then looks to like it just reboots back into windows.

Any advice would be great, kinda hard to see if im dealing with an network card issue, Ghostcast server issue, or is symantec simply throwing a wrench at me because im merely using the trial version to evaluate. Any help would be great Thanks,

-- Josh

Hi Josh,

It looks like something on the console machine blocks the communication with the client. Do you have a firewall on the console machine? If yes, can you check if 'Symantec GhostCast Server' is added to the exceptions list? If it is not, add it to the exceptions list and try again. You can also try with the firewall off.


Hope this helps,

Adina

There is no firewall, and no anti-virus installed, I've turned off the window's firewall.

I've been able to capture and restore data to the machine, however everything else seems to fail when it reaches the " CLONE " step.

Still searching for an answer.

seems like it's a multicasting issue. Are the console and the client both on the same subnet? Try directed broadcasting. You might want to check if your company's router is configured for multicasting.

Both client and server are on the same subnet and are in the same IP range.
We are using a

10.1.1.X IP address
255.255.0.0 Subnet.

Tried using the direct broadcast and it yielded the same result of still failing during the clone step and unable to connect to the ghostcasting server. I really dont understand why this is so hard the client is installed I pushed the client FROM the server and creating this image should really be a simple thing.

Here is my full error log
*********************************
*********************************
Date : Mon Feb 12 10:11:18 2007
Error Number: (10030)
Message: Unable to establish contact with session <ASIITPULL13>.
Check that the GhostCasting Server application is ready
to accept clients!
Version: 11.0.0.1502 Trial (Dec 4 2006, Build=1502)
OS Version: DOS v7.10
Command line arguments: -Z1 -clone,src=1,mode=create,dst=@MCASIITpull13 -batch -igb -sgt
Active Switches :
AutoName
PathName :
DumpFile :
DumpPos : 0
FlagImplode : 2
FlagExplode : 0

CloneSrc : 1
BatchPartSrc : 0
BatchPartMSrc :

CloneDst : @MCASIITPULL13
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
CheckCloneSwitches
ProcessArgumentsToPass
sub_main
main

Call Stack
0x003964fc
0x000b6bb1
0x000b63ec
0x000b5ac7
0x000b76ce
0x000093a6
0x0000ca55
0x000114f4
0x00011675
0x00004ac9
0x00003f2f
0x0039f728
End Call Stack


Start heap available: 56688640
Cur heap available: 56492032
Total Memory: 65994752

Allocated
1024 DpmiDjgpp.cpp:56
33504 ghost.cpp:1394
48 DiskDriveAccessExInt13.cpp:139
528 IdeDmaServerPci.cpp:127
528 IdeDmaServerPci.cpp:127
Free
64 GetDriveType.cpp:111
80 DiskDriveAccessExInt13.cpp:102
512 DiskDriveAccessInt13.cpp:184
32768 MsdosFile.cpp:368

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 SAMSUNG HD080HJ/P S0DEJ1GLA63491
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 156301488
Bytes per Sector 512
MB 76319
Successful IO Count 0

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

IDE using UDMA (Active)
Total Sectors 156301488
Bytes per Sector 512
MB 76319
Cylinders 16383
Heads 16
Sectors per Track 63
Successful IO Count 66

Floppy Drives

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

Conventional Memory
Initial Conventional Memory Size = 357712
Current Conventional Memory Size = 222720

Allocated
1024 DpmiDjgpp.cpp:56
33504 ghost.cpp:1394
48 DiskDriveAccessExInt13.cpp:139
528 IdeDmaServerPci.cpp:127
528 IdeDmaServerPci.cpp:127
Free
64 GetDriveType.cpp:111
80 DiskDriveAccessExInt13.cpp:102
512 DiskDriveAccessInt13.cpp:184
32768 MsdosFile.cpp:368


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

Fixed Drives

Drive 128 SAMSUNG HD080HJ/P S0DEJ1GLA63491
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 156301488
Bytes per Sector 512
MB 76319
Successful IO Count 0

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

IDE using UDMA (Active)
Total Sectors 156301488
Bytes per Sector 512
MB 76319
Cylinders 16383
Heads 16
Sectors per Track 63
Successful IO Count 66

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: 0x2990
(0x00, 0x02, 0x01): IRQ: 0x00, INT#: -, Link: 0x00
Class: Display, SubClass: Other Display
Vendor: 0x8086, Device: 0x2993, RoutePINS: 0x60, 0x61, 0x00, 0x00,
(0x00, 0x1c, 0x00): IRQ: 0xff, INT#: -, Link: 0x00
Class: Bridge, SubClass: PCI/PCI
Vendor: 0x8086, Device: 0x283f, 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: 0x2814, 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: 0x2992, RoutePINS: 0x60, 0x61, 0x00, 0x00,
(0x00, 0x03, 0x00): IRQ: 0x05, INT#: A, Link: 0x60
Class: Simple Com, SubClass: Other Com
Vendor: 0x8086, Device: 0x2994, RoutePINS: 0x60, 0x61, 0x62, 0x00,
The following hard wire-ord devices share IRQ 5:
(0x00, 0x1f, 0x02): IRQ: 0x05, INT#: B, Link: 0x62
Class: Mass Storage, SubClass: IDE Controller
Vendor: 0x8086, Device: 0x2820, RoutePINS: 0x61, 0x62, 0x62, 0x00,
The following hard wire-ord devices share IRQ 10:
(0x00, 0x19, 0x00): IRQ: 0x0a, INT#: B, Link: 0x63
Class: Network, SubClass: Ethernet
Vendor: 0x8086, Device: 0x104a, RoutePINS: 0x63, 0x63, 0x00, 0x00,
The following hard wire-ord devices share IRQ 11:
(0x00, 0x1a, 0x00): IRQ: 0x0b, INT#: A, Link: 0x68
Class: Serial Bus, SubClass: USB UHCI
Vendor: 0x8086, Device: 0x2834, RoutePINS: 0x68, 0x69, 0x6a, 0x00,
(0x00, 0x1d, 0x00): IRQ: 0x0b, INT#: A, Link: 0x68
Class: Serial Bus, SubClass: USB UHCI
Vendor: 0x8086, Device: 0x2830, RoutePINS: 0x68, 0x69, 0x6a, 0x6b,
(0x00, 0x1d, 0x07): IRQ: 0x0b, INT#: A, Link: 0x68
Class: Serial Bus, SubClass: USB EHCI
Vendor: 0x8086, Device: 0x2836, RoutePINS: 0x68, 0x69, 0x6a, 0x6b,
The following hard wire-ord devices share IRQ 5:
(0x00, 0x1a, 0x01): IRQ: 0x05, INT#: B, Link: 0x69
Class: Serial Bus, SubClass: USB UHCI
Vendor: 0x8086, Device: 0x2835, RoutePINS: 0x68, 0x69, 0x6a, 0x00,
(0x00, 0x1b, 0x00): IRQ: 0x05, INT#: A, Link: 0x69
Class: Multimedia, SubClass: Unknown Multimedia
Vendor: 0x8086, Device: 0x284b, RoutePINS: 0x69, 0x00, 0x00, 0x00,
(0x00, 0x1d, 0x01): IRQ: 0x05, INT#: B, Link: 0x69
Class: Serial Bus, SubClass: USB UHCI
Vendor: 0x8086, Device: 0x2831, RoutePINS: 0x68, 0x69, 0x6a, 0x6b,
The following hard wire-ord devices share IRQ 10:
(0x00, 0x1a, 0x07): IRQ: 0x0a, INT#: C, Link: 0x6a
Class: Serial Bus, SubClass: USB EHCI
Vendor: 0x8086, Device: 0x283a, RoutePINS: 0x68, 0x69, 0x6a, 0x00,



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

Volume 1
VolumePos: 1.1:
DriveLetter:
Description: 19.53GB Primary Disk 0 Offset 31.50KB 19.53GB SAMSUNG HD080HJ/P S0DEJ1GLA63491
Type: fsfNtfsWindowsXP
Name:

Volume 2
VolumePos: 1.2:
DriveLetter:
Description: 14.65GB Logical Disk 0 Offset 19.53GB 14.65GB SAMSUNG HD080HJ/P S0DEJ1GLA63491
Type: fsfNtfsWindowsXP
Name: Recovery

Volume 3
VolumePos: 1.3:
DriveLetter:
Description: 40.34GB Logical Disk 0 Offset 34.19GB 40.34GB SAMSUNG HD080HJ/P S0DEJ1GLA63491
Type: fsfNtfsWindowsXP
Name:


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


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

Filesystem Index: 0
Filesystem Descriptor:
ID's:
ID Type: 2
ID: A:
DriveType: 2
No FilesystemInfo structure.
Filesystem has no VolumePtr

Filesystem Index: 1
Filesystem Descriptor:
ID's:
ID Type: 2
ID: C:
DriveType: 4
No FilesystemInfo structure.
Filesystem has no VolumePtr

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

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

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


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

Josh, multicasting shouldn't be a problem, since you are creating an image and, in this case, unicast is used. Since the firewall is off and it doesn't block the connection, the most likely culprit is the network card. Can you please check what is the network card of the client machine and what is the driver the console is using? To check what driver is used, open the client properties (double click on the client) in the 'Default' folder, under 'Machine groups', go to 'Client' tab and see what is the template used for the network card. Also, is it a suggested template or a manually selected one?
To rule out any other cause, try to create the image using GhostCasting. To do this, start a GhostCast Server session from the console machine, enter all the required parameters to dump the image and then start a GhostCast session from the client (select GhostCasting from the Ghost menu) and use the same session name you specified in the console. It should work.

Hope this helps,
Adina

After a little more digging I finally have an answer to my problem.

Yes Adina you are correct with the driver. That needed to be done in order to accomplish what I wanted to do.

I did that and the clone process still failed.

So I did some extra looking on the client machine and looked at some of the running processes. Word to the wise, un-installing all firewall's is not enough. I figured out that all real time scanning must be disabled in order for a remote image task to accomplish in Ghost Solution suite. So even though you may disable all firewall's you actually might have too look beyond that in order to get your connection to happen. Especially with any anti virus that may be real-time scanning.

THANKS to everybody that took a look at this post I appreciate it. Hopefully this helps someone else.

Hi Josh,

I'm glad to hear it is working now. Just for the interest, what kind of real time scanning did you have on the console machine?

Adina

Mcafee on-access scan. I really don't care for Mcafee at all, but this was what the company had in place before my arrival.

hmm... Ironically, I have Symantec Antivirus 10.5 Corp and it has the real-time scan process called, rtvscan.exe and i'm having the same exact problem. I'll disable it and give it a try..

The question I would have is this, how can you get around that real time scan, if you want to automate a process of imaging the hard drive and restoring it in one task, if you have to disable your real time scan each time you want to do that. Granted I could go in and manually turn it off each time I wanted to do it, but... multiply that x200 machines... I must be missing something there. Perhaps there is a place where you can configure to exclude certain things in your real time scan but I haven't dug that far yet.

Thank you for the information. I will do some tests regarding this situation because a run time scan should only slow down the process, not stop it. Also, the scan is probably happening on the console machine, since the client goes to DOS, so even if you have multiple clients, you should only turn it off on the console.

Adina