Ghost Solution Suite

I am trialing Symantec Ghost 8.3 in the hope of using it to ghost an image to 12 identical PC's for a Cyber Cafe. I am trying to create an image. The test client PC has no A drive and doesn't have a CD capable of burning so I was hoping to set it up via lan. The test PC only has Windows XP Home addition loaded. On the server (Windows XP Prof) I set up the GhostCast Server ready to accept clients to create the image. When I use my boot CD on the client all looks good it gets it's IP address from DHCP and allows me join the session and set up the image properties. Back at the ChostCast server I can see the client's IP address, MAC Address and the status is "In Progress" but this is as far as it goes. No data is transfered accross the lan. Speed, MB Transmitted, Percent Complete are all zero's. Connected clients is 1. Back at the client on the status line at the bottom reads "Adding MFT table file to image". Still waiting for something to happen. Any help would be appreciated.

You need to wait for it to time out then take a look at the ghost error log. If you have the console installed why not install the client software on the model machine and run the image create task from the console? I'm not saying it will fix the problem but I find it easier than working with boot disks or cds the whole time

The following is parts of the generated GhostLog.txt file, I haven't included it all because it's quite a large file.

Log Level All
8669359 GhostSrv 8.3.0.1331
Fri Nov 10 09:54:57 2006

8675359 Server is in image dump mode - will force client into unicast mode
Initialising RML
rml_get_local_interfaces found these IP addresses:
192.168.1.11
RML Initialised
8675375 RML socket send buffer size set to 549504
Setting UDP socket receive buffer size to 20034
UDP socket receive buffer size set to 20034
RML socket receive buffer size set to 17172
8675390 Throttle value:0 mb/min
Length of tick in seconds:0.001000
Ticks per throttle bucket:15
Throttle byte count limit = 0
Throttle byte count limit = 0
Throttle byte count limit = 0
Throttle byte count limit = 0
Throttle byte count limit = 0
Throttle byte count limit = 0
Throttle byte count limit = 0
Throttle byte count limit = 0
Throttle value:0 mb/min
Length of tick in seconds:0.001000
Ticks per throttle bucket:15
Throttle byte count limit = 0
Throttle byte count limit = 0
Throttle byte count limit = 0
Throttle byte count limit = 0
Throttle byte count limit = 0
Throttle byte count limit = 0
Throttle byte count limit = 0
Throttle byte count limit = 0
RML socket send buffer size set to 4194304
Server multicast address set to 224.77.25.152
Throttle value:0 mb/min
Length of tick in seconds:0.001000
Ticks per throttle bucket:15
Throttle byte count limit = 0
Throttle byte count limit = 0
Throttle byte count limit = 0
Throttle byte count limit = 0
Throttle byte count limit = 0
Throttle byte count limit = 0
Throttle byte count limit = 0
Throttle byte count limit = 0
Bound RML socket to 0.0.0.0:1487
Setting multicast scope to 16
State was 0, now 1
Bound TCP socket to 0.0.0.0:1488
8675921 Bound UDP socket to 0.0.0.0:6666
Interface 192.168.1.11 (0) ws2AddMembership succeeded
8726781 R: LEN: <277> SESSION: <El> FROM: <192.168.1.12:1025>
S: LEN: <260> SESSION: <El> TO: <192.168.1.12:1025>

8732046 Wait(0) returned (RW) after 0 ticks

R: SYN SEQ=0 ACK=0 WIN=17172 LEN=39 ADDR=192.168.1.12:7777
Recv would block
Telling client (192.168.1.12) to use Unicast data transfer mode

S: SYN ACK TAK SEQ=0 ACK=1 WIN=17172 LEN=41 ADDR=192.168.1.12:7777
Sent second packet unicast
State was 1, now 3

Wait(1000) returned (R) after 16 ticks

5876406 timed out after 1000 ticks

Wait(1000) timed out after 1000 ticks

5877406 Wait(1000) timed out after 1000 ticks

5878406 Wait(1000) timed out after 1000 ticks

5879406 Wait(1000) timed out after 1000 ticks

5880406 Wait(1000) timed out after 1000 ticks

-------- Many more lines of the same text --------------

5892406 Wait(1000) returned (R) after 875 ticks

5893281 R: ACK TOK SEQ=33202 ACK=29 WIN=17172 LEN=1431 ADDR=192.168.1.12:7777
Missing packets

S: ACK SEQ=29 ACK=31771 WIN=17172 LEN=0 ADDR=
Recv would block

Wait(1000) returned (R) after 0 ticks

R: ACK TOK SEQ=31771 ACK=29 WIN=17172 LEN=1431 ADDR=192.168.1.12:7777

S: ACK SEQ=29 ACK=34633 WIN=17172 LEN=0 ADDR=
Recv would block

Wait(1000) returned (R) after 15 ticks

5893296 R: ACK TOK SEQ=36064 ACK=29 WIN=17172 LEN=1431 ADDR=192.168.1.12:7777
Missing packets

S: ACK SEQ=29 ACK=34633 WIN=17172 LEN=0 ADDR=
Recv would block

Wait(1000) timed out after 1000 ticks

5894296 Wait(1000) timed out after 1000 ticks

5895296 Wait(1000) timed out after 1000 ticks

-------- Many more lines of the same text --------------

5951296 Wait(1000) timed out after 1000 ticks

5952296 Wait(1000) returned (R) after 860 ticks

5953156 R: ACK TOK SEQ=36064 ACK=29 WIN=17172 LEN=1431 ADDR=192.168.1.12:7777
Missing packets

S: ACK SEQ=29 ACK=34633 WIN=17172 LEN=0 ADDR=
Recv would block

Wait(1000) timed out after 1000 ticks

5954156 Wait(1000) timed out after 1000 ticks

5955156 Wait(1000) timed out after 1000 ticks

-------- Many more lines of the same text --------------

6011156 Wait(1000) timed out after 1000 ticks

6012156 Wait(1000) returned (R) after 859 ticks

6013015 R: ACK TOK SEQ=36064 ACK=29 WIN=17172 LEN=1431 ADDR=192.168.1.12:7777
Missing packets

S: ACK SEQ=29 ACK=34633 WIN=17172 LEN=0 ADDR=
Recv would block

Wait(1000) returned (R) after 0 ticks

R: ACK TOK SEQ=34633 ACK=29 WIN=17172 LEN=1431 ADDR=192.168.1.12:7777

S: ACK SEQ=29 ACK=37495 WIN=17172 LEN=0 ADDR=
Recv would block

Wait(1000) returned (R) after 16 ticks

6013031 R: ACK TOK SEQ=38926 ACK=29 WIN=17172 LEN=1431 ADDR=192.168.1.12:7777
Missing packets

S: ACK SEQ=29 ACK=37495 WIN=17172 LEN=0 ADDR=
Recv would block

Wait(1000) timed out after 1000 ticks

6014031 Wait(1000) timed out after 1000 ticks

6015031 Wait(1000) timed out after 1000 ticks

-------- Many more lines of the same text --------------

6549968 Wait(1000) timed out after 1000 ticks

6550968 Wait(1000) returned (R) after 875 ticks

6551843 R: ACK TOK SEQ=47512 ACK=29 WIN=17172 LEN=1431 ADDR=192.168.1.12:7777
Missing packets

S: ACK SEQ=29 ACK=46081 WIN=17172 LEN=0 ADDR=
Recv would block

Wait(1000) returned (R) after 0 ticks

R: ACK TOK SEQ=46081 ACK=29 WIN=17172 LEN=1431 ADDR=192.168.1.12:7777

S: ACK SEQ=29 ACK=48943 WIN=17172 LEN=0 ADDR=
Recv would block

Wait(1000) returned (R) after 16 ticks

6551859 R: ACK TOK SEQ=50374 ACK=29 WIN=17172 LEN=1431 ADDR=192.168.1.12:7777
Missing packets

S: ACK SEQ=29 ACK=48943 WIN=17172 LEN=0 ADDR=
Recv would block

Wait(1000) timed out after 1000 ticks

6552859 Wait(1000) timed out after 1000 ticks

6553859 Wait(1000) timed out after 1000 ticks

-------- Many more lines of the same text --------------

7000765 Wait(1000) timed out after 1000 ticks

7001765 Wait(1000) returned (R) after 31 ticks

7001796 R: ACK TOK SEQ=1947880 ACK=29 WIN=17172 LEN=1431 ADDR=192.168.1.12:7777
Missing packets

S: ACK SEQ=29 ACK=1946449 WIN=17172 LEN=0 ADDR=
Recv would block

Wait(1000) timed out after 1000 ticks

7002796 Wait(1000) timed out after 1000 ticks

7003796 Wait(1000) timed out after 1000 ticks

7004796 Wait(1000) timed out after 1000 ticks

7005796 Wait(1000) timed out after 1000 ticks

7006796 Wait(1000) timed out after 1000 ticks

7007796 Wait(1000) timed out after 1000 ticks

7008796 Wait(1000) timed out after 1000 ticks

7009796 Wait(1000) timed out after 1000 ticks

7010796 Wait(1000) timed out after 1000 ticks

7011796 Wait(1000) timed out after 1000 ticks

7012796 Wait(1000) timed out after 1000 ticks

7013796 Wait(1000) timed out after 1000 ticks

7014796 Wait(1000) timed out after 1000 ticks

7015796 Wait(1000) returned (R) after 63 ticks

7015859 R: RST ACK SEQ=1949311 ACK=29 WIN=0 LEN=0 ADDR=192.168.1.12:7777
ConnectionState was 4, now 13
State was 4, now 13
rml_wait failed: connection reset
RML_recv failed: Connection reset by peer.
rml_wait failed: connection reset


RML Statistics

Retransmits on Timeout: 4
Packets Missing/Out of Order: 2110

End RML Statistics

Shutting down RML
RML shutdown

Log Level NoneMessage was edited by:
Lee Firth

I have experienced a similar problem with Broadcom Drivers. The driver is loaded and apears to be correct acording to Ghost however the actual image deployment hangs and does not progress after starting. I'm afraid I do not have to hand the exact details but I can tell you it is a version of the Broadcom net extreme driver and changing drivers will cure this issue.

Thanks Gary