Ghost Solution Suite

I am running a trial version of Ghost solution suite (Version 11.5.1.2266) I am trying to send an image to some PC's on our test net, which has an existing PXE server. Everything starts fine but before we get to 10% the client says it needs to open the second spanned image and I have to cancel the image. The recieving disk is 100 gig, the image file is our current win7 image imported from another server (Still runs fine there). The log files look like this: 

        R:         ACK             TOK     SEQ=967 ACK=2148644735 WIN=57240 LEN=14 ADDR=130.85.82.123:7777
           Congestion window 4897
           RTT for 2148644725 is 8 ticks
           Retransmit timeout 32 = 9 + 4 * 4
           Recv would block

           S:         ACK                     SEQ=2148644735 ACK=981 WIN=57240 LEN=10 ADDR=[ALL]
           Timing of 2148644735 commenced

           Wait(32) returned (R) after 16 ticks

 525285359 R:         ACK             TOK     SEQ=981 ACK=2148644745 WIN=57240 LEN=10 ADDR=130.85.82.123:7777
           Congestion window 4907
           RTT for 2148644735 is 24 ticks
           Retransmit timeout 40 = 11 + 4 * 7
           Recv would block

           Wait(200) timed out after 203 ticks
 525285562 Acknowledgement timeout

           S:         ACK                     SEQ=2148644745 ACK=991 WIN=57240 LEN=0 ADDR=[ALL]

           Wait(1000) timed out after 1000 ticks

 525286562 Wait(1000) timed out after 1000 ticks

 525287562 Wait(1000) timed out after 1000 ticks

 525288562 Wait(1000) timed out after 1000 ticks

 525289562 Wait(1000) timed out after 1000 ticks

 525290562 Wait(1000) timed out after 1000 ticks

 525291562 Wait(1000) timed out after 1000 ticks

This goes on for a while, then:

525731656 Wait(1000) timed out after 1000 ticks
 525732656 RML_recv failed: No Error

           S: RST                             SEQ=2148644745 ACK=991 WIN=0 LEN=0 ADDR=130.85.82.123:7777
           ConnectionState was 4, now 12
           State was 4, now 12

           RML Statistics

                   Retransmits on Request:          1
                   Retransmits on Timeout:        215
                       Zero Window Probes:         13

           End RML Statistics

           Shutting down RML
 525732859 RML shutdown

I think the last part is me going and canceling the image at the client.

I don't know where to check if spanning is enabled, but it shouldn't need to be.

Any help would be appreciated.

Brian

I forgot to mention that this process seems to create a 0kb file which says it is a ghost spanned image in the same folder with the original image and with a name derived from the original.

Is the image you have imported from another server an actual Ghost image created with Ghost Solution Suite?  Is it spanned?

Are your test machines PXE booting to DOS or WinPE?  If WinPE, has this been created with Ghost Boot Wizard, and if so, have you added the appropriate VISTA 32 bit drivers for the NIC and SATA chipsets?

Is the image you have imported from another server an actual Ghost image created with Ghost Solution Suite?

Yes.

Is it spanned?

No

Are your test machines PXE booting to DOS or WinPE?  

WinPE

If WinPE, has this been created with Ghost Boot Wizard, and if so, have you added the appropriate VISTA 32 bit drivers for the NIC and SATA chipsets?

Don't Know, Is there a good way to check?

Your "Don't know" - does it apply to whether WinPE was created with Ghost Boot Wizard, or whether Vista 32 bit drivers were added?

Since both steps would have to have been carried out by however set up your trial version, are you able to ask them?

One of the issues that arises when trying to image over a network is that the network client is unable to determine whether the machine "serving" the file is restricted to 2Gb files or not. For example, you could use a workstation with a FAT32 file system as a Ghost "server".  Since your image is not spanned, and presumably over 2Gb, the Ghost client reaches 2Gb and then asks for the next file.  If you can create an image of your master system using 2Gb spans and then retest with that image, you may have better success.