jamin100 Posted April 10, 2008 Posted April 10, 2008 (edited) Hi guys, Right, I have 30 new PC's (all identical) that i have dotted around the school which now need imaging. I have installed all our software onto a one of the machines, sysprep'd it and imaged it with Symantec ghost (version 11) Now, I thought that before i deployed the image out to all the required machines, i'd test a couple first just to make sure everything was ok. So i have got 3 machines in 1 classroom all connected to the network via the same patch panel and switch. I start a ghost cast session on all 3 machines and deploy the image. I use multicast for this session. Machine 1 - works fine. Image has copied over no problems Machine 2 & 3 have failed. They are reporting that the session has timed out. So i try again exactly the same with the 2 machines and the same thing happens again. They connect to the session fine for a few minutes copy 400-500MB of data across then suddenly time out. Ok, So i try the session on the clients indivadualy thinking that maybe the data is getting swamped over the network and not getting through. Same result.. Times out. Next i try doing a unicast session on both machines. Machine 2 Fails and times out but machine 3 complete's fine without any problems. So I try the same procedure on Machine 2.. Again it times out. Finally i try Direct Broadcast on machine 2 and yet again it times out. So for some reason I'm getting some strange problems when ghosting over the network. I have performed quite a few ghost sessions on this network in the past and this is the first problem i am having. Here's what i have figured out so far. 1. All clients are picking the correct IP addresses and the ghost cast sessions start fine and data does start copying onto the machines. 2. All clients are in the same subnet 3. All clients are connected to the network via the same gigabit switch and the same patch panel. 4. I have tried the machines in different network sockets .. Same problem.. 5. The Image is stored on the server hard drive and not a USB drive attached to the server. The network is a vanilla Windows 2003. With a dual core Xeon processor and 2GB RAM. I performed the images at 3:45 when there were only 5 machines turned on and using the network for minimal work (ie they were all using word) Does anyone have any idea? Thanks Ben Edited April 10, 2008 by jamin100
linkazoid Posted April 10, 2008 Posted April 10, 2008 I'm having the same problems as you describe... are you using Ghost Solution suite 2 by any chance? I think it may be to a recent update.... if you find a solution then please post it here... i will do likewise. Mike
jamin100 Posted April 10, 2008 Author Posted April 10, 2008 (edited) No, I don't think im using solution suite 2... Just Symantec Ghost 11. I havn't done any software updates on ghost anyway so unless it does it automatically ???? But yeh if i find a solution in the meantime i will post i back here.... Thanks Ben EDIT... Just some more info... It seems to keep failing at the same point. On the bottom of the client it reads "Restoring... remaining NTFS MFT files.". The computer then hangs and i have to hold the power button down to restart the PC Edited April 10, 2008 by jamin100
DMcCoy Posted April 10, 2008 Posted April 10, 2008 Dead drive? Thats normally the issue when ghost repeately dies while imaging
jamin100 Posted April 10, 2008 Author Posted April 10, 2008 I wouldnt have thought so. The drives are brand new as the machines are... I'll try a few other machines over the network tomorrow and see what happens. The machines did boot to the pre installed XP before i tried to ghost them
linkazoid Posted April 10, 2008 Posted April 10, 2008 EDIT... Just some more info... It seems to keep failing at the same point. On the bottom of the client it reads "Restoring... remaining NTFS MFT files.". The computer then hangs and i have to hold the power button down to restart the PC This is the same for me... but only when i'm creating the image file.. it always stops at about 450Mb.. this was when i was using the automated client method with Ghost Solution Suite.. used the boot cd and created the session manually and it worked fine..
eejit Posted April 11, 2008 Posted April 11, 2008 I *think* that Ghost 11 and Solution Suite 2 are the same thing. (and we've had problems with it too - went back to 8 and everything worked fine (if you have the switches for SATA drives))
jamin100 Posted April 11, 2008 Author Posted April 11, 2008 (edited) I'm using a universal Packet Driver CD from ghost 8.3 that i have used before on many other machines with no problems... Going to make a new bootable CD now and see if that makes a difference. Edited April 11, 2008 by jamin100
jamin100 Posted April 11, 2008 Author Posted April 11, 2008 (edited) OK, that didnt work either... The connection has timed out again after transmitting 741MB to 1 client.... The only thing different about these desktops is that they have SATA drives. But i imaged some 30 laptops about 3 weeks ago with sata drives and had no problems with those. EDIT: I have now tried connecting one of the new PC's to the core switch (same as the server) and still have the same problem. This is really starting to F*** me off. Edited April 11, 2008 by jamin100
Sirbendy Posted April 11, 2008 Posted April 11, 2008 We had some funky issues with Ghostcast 11 and Ghost 8.x about 12 months ago...same sort of thing. IIRC, it was switch config. As a bypass while waiting for LEA to get round to a solution I set up a linux SME server on a spare box hosting the image, and used the "Universal MS Network boot disk" to boot and map the machines to that..that worked fine over mapped drives. It's all been resolved now though..
krisd32 Posted April 11, 2008 Posted April 11, 2008 Could be something to do with the spanning tree protocol on your switches? have a look on your switches to see if its enabled.
jamin100 Posted April 11, 2008 Author Posted April 11, 2008 Its not the switches. I think i MAY and i mean MAY have solved the problem which i think was to do with a IRQ conflict between two of the devices. I'm ghosting a machine now to see how it reacts but its taking ages. All other machines that i ghost usually take about 10-15 minutes. This is taking about 45 minutes over a multicast session. As soon as it finishes or fails i'll let you know.
broc Posted April 11, 2008 Posted April 11, 2008 We have had similar problems caused by down-level NDIS2 network drivers.
jamin100 Posted April 11, 2008 Author Posted April 11, 2008 Yeh, I've downloaded the NDIS drivers for the NIC in these machines and it seems to be going ok but really slow! Its a 1GB network allover and the highest speed its reached is 160MB/s But at least its working. Anyone know why its slow? I'm only imaging 1 machine which is connected to the same switch as the server. I've tried both unicast and multicast.
DMcCoy Posted April 11, 2008 Posted April 11, 2008 Yeh, I've downloaded the NDIS drivers for the NIC in these machines and it seems to be going ok but really slow! Its a 1GB network allover and the highest speed its reached is 160MB/s But at least its working. Anyone know why its slow? I'm only imaging 1 machine which is connected to the same switch as the server. I've tried both unicast and multicast. Is it a broadcom NIC?
jamin100 Posted April 11, 2008 Author Posted April 11, 2008 Is it a broadcom NIC? No Realtek. But i've read about problems with the broadcom NIC's too
PeterW Posted April 11, 2008 Posted April 11, 2008 No Realtek. But i've read about problems with the broadcom NIC's too Do you know which version of the realtek lan rom you have it will be something like 2.04, 2.06 etc?
tmcd35 Posted April 11, 2008 Posted April 11, 2008 Pretty much all the Ghost problems we've had here have been traced back to drivers. Usually, either changing to the latest version of the driver or using a Universal Packet driver has solved the problems. Sometimes changing from a PC-Dos based boot image to a MS-Dos based one, or vice-versa, has also solved time outs with Ghost.
jamin100 Posted April 11, 2008 Author Posted April 11, 2008 Do you know which version of the realtek lan rom you have it will be something like 2.04, 2.06 etc? Version 1.2 from LINK Which says NDIS2 driver for DOS (Support MSclient, Lantastic, Lanman, Norton Ghost) The card is a REALTEK RTL8168/8111 PCI-E Gigabit NIC
Ex-MGSTech Posted April 11, 2008 Posted April 11, 2008 Do your switches have any kind of storm control, or multicasting restrictions? Steve
jamin100 Posted April 11, 2008 Author Posted April 11, 2008 I doubt it. There only DLink DGS-1248T's Cheap and Cheerfull + i can ghost another make of PC ate 900MB per sec (ish)
naodwalk Posted March 14, 2009 Posted March 14, 2009 I don't know if this will help, but try ghostcasting the image of the client machine through the network to the server and then from the server to the client machine. It worked for me
graywoodford Posted May 29, 2009 Posted May 29, 2009 we had a few issues with this and for us it was a setting in the switch restricting mulicast session, as soon as we logged on and turned that off we ran normally and worked no issues.
theBear455 Posted August 26, 2011 Posted August 26, 2011 I had this same issue with my Ghost session timing out. First with two Dell Latitude 2120 laptops at the same time, then with each one individually. The really odd thing was, when I captured the image using a third 2120 laptop, it was slow, but completed perfectly. After reading this thread, I tried a couple of different boot medias (flash drive, boot CD, etc.), but all crashed with the time out error on the Ghost console. The client on the laptops just froze. And this happened at less than two minutes into the image, sometimes not even making 1%. I decided to download the latest Broadcom NetXtreme driver from Dell's website. Sure enough, the B57.dos (NDIS2) driver date was newer (12/10/2010) than what I had been using. I am using Ghost Solution Suite 2.5 with Ghost version 11.5.0.2113. I created a new boot CD with the Ghost console. As of now, my image is 50% along, 34 minutes in, somewhat slow, but working so far. So even though the old driver version I was using did make the connection, the new version appears to have resolved the time out problem.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now