I'm attempting to Image a box running Win2000 into an image file on another win2000 box over the network. I created two boot disks with Norton ghost 2003 boot disk wizard, each with packet drivers for there respective network cards. When I boot from the disk everything kicks in fine. Each are running at 100 with Full Duplex. I set Norton to go and it starts to ghost the 750 Meg's of information on the drive into a image file on the other box. I created the image successfully my problem I raise is it took 14 hours to ghost 750 Meg's from one computer to the other!! I know this can not be right. I have search all the FAQs and tech support on the Norton website and have had no luck in finding a solution. Does anybody know why this is happening and even better, a solution. The two computers are networked via a SMC router. I have had no problems in the past with my network, it is blazing fast, normally.

had the same problem, contacted Symantec, they told me to set up the cards as 10 MB and half duplex. these are parameters that are setup on your floppies for the network cards you use. if you are still having problems or cannot figure out how to do this, contact Symantec, they replied to me OK. Al

Check to see if there are any multicast filters running on the SMC router.

For some reason, and it is still unknown to Symantec, here is how I got it going in my shop. If you are casading your swtiches, for sure it will be slower. To fix this, put your pc and the server(the one that holds your ghost image file) in the same switch. Configure both ports at 100 full. If you still have problem, configure the server at 100 full, pc at 10 half. If you have to cascade switches, you might be(sometimes, not always) better off at 10 half. But if you do multicast, do not mix 10 half and 100 full together, it will be slow for sure. You are better off to stay with all at 10 half, or all at 100 full. Also, if you do multicast with ghost, make sure your switch and router have igmp/cgmp enable, otherwise every port in your network will feel that multicast traffic.

I had this same problem in my lab, there was a fix on microsoft web site. It was a known issue, This only happens in DOS mode. The problem has to do with default packet sizes set in the registry. Once I ran the patch it worked like a champ. Try searching Microsofts knowledge base