Do you know which version of the realtek lan rom you have it will be something like 2.04, 2.06 etc?No Realtek. But i've read about problems with the broadcom NIC's too
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.
Do your switches have any kind of storm control, or multicasting restrictions?
I doubt it. There only DLink DGS-1248T's
Cheap and Cheerfull
+ i can ghost another make of PC ate 900MB per sec (ish)
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
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.
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 18.104.22.1683. 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.
There are currently 1 users browsing this thread. (0 members and 1 guests)