Summary: I successfully backed up and restored a disk image on a notebook computer across a network share. I needed to upgrade my notebook computer hd to same model, same size, but faster speed. The notebook only has room for 1 drive bay, and I don't have an external. So, I needed to access my desktop machine which had an extra drive on it currently utilized for TI backups for it. This would require using TI through the home lan which TI does - correct? Basically I figured out there was no way to target the notebook from the desktop so I decided to use the TI Recovery Disk on cd in the notebook to target the desktop. I started TI up fine on the notebook, and I needed to use Clone because basically that is what I was doing...cloning the hardrive within it. However Clone will not work because it requires all drives to be mounted local. So turns out I needed to do an image backup and restore. Thought #1: Shouldn't the Clone function also be a network function? The problem came in when I tried to connect remotely to the drive on the desktop through the network. I tried numerous ways / settings to get TI's connectivity up using what I believe are the correct values and I could NEVER get it to work. For some reason DHCP was also showing up as unavailable so I was manually entering values. I followed recommendations from other forum posts and did a long qualification of the server, share, gave proper permissions, etc but no luck and no DHCP. Fortunately for me a few months ago as I wandered the internet I came across the BartPe tool on my own. It appeared to me super nifty and so I had set it up and tested it. Bart gave me access to internet, lan, file system, virus scanner, nero, and other things. I had remembered that there was a plug in for Disk Director too, and I figured I could also use it to start True Image. I also noticed that Acronis has a Bart plugin for TI - so I downloaded and installed it too. This came up without a hitch. I messed around with the network some more only to find I still couldn't quite get it to work. Then I remembered that a few months ago when I did my setup I ended up using an ethernet cable rather than the wireless network. So, I plugged that in and Bart connectivity was fully available. I backtracked and restarted the notebook using TI's Recovery Disk and attempted connectivity with the ethernet cable (as opposed to wireless), but still no luck. The whole set up for TI's network is very rudimentary and needs much improvement. Fortunately Bart's abilities in this regard are fairly robust. So here my recommendation is to avoid TI's network capability (or lack thereof) and just use Bart with TI as a plugin. I booted Bart and loaded TI - found the remote network share and after providing it sharing and access authorization on the desktop side was able to start the Create Image function. TI backed it up without errors - apparently flawlessly as far as I could tell. If there was a verify feature I didn't see this so that is some concern to me as to if TI does a compare of source and target as it processes to insure no lost / corrupt bytes. After that I removed the old hd from the notebook, and put the new one in. I started Bart and TI back up. Note that here I had been concered that Bart plugins were actually accessing the underlying application on the related hard disk where the app had been installed. The Bart disk I have is only a cd with ~700mb of space, so it just didn't seem right that all these applications would fit on the small Bart cd. However when I put the new drive in the notebook and started TI it worked without a hitch. So, apparently Bart doesn't access these similar to a shortcut, but instead has the full functionality on the small cd. Amazing! Anyway, Bart and TI came up, network came up, and I started the restore re-building the notebook hard drive on the new disk from the copy stored on the network. That process also went flawlessly as far as I can tell. So at the moment I am very happy . Recommendations: 1) Acronis really needs to improve this network ability. Perhaps TI 9 (which I don't own) has addressed this already? 2) If #1 hasn't been done, don't even mess with getting TI's network to work. Just use BartPe with a TI plug in. 3) Connect to network using direct ethernet cable, avoid wireless networking. Observations / Questions: 1) When the notebook with the newly rebuilt hard drive first booted, I was surprised to see that XP SP2 noticed the drive and loaded drivers, but the old drive was 4200rpm and the new is 5200rpm so perhaps it realized something was slightly different and it needed to reload. Wonder if it loaded the correct drivers and correct mode of operation? 2) When the notebook (with recently re-created hd) started up I am wondering if the background desktop image is of lower quality. Seems it appears to have more noise than it use to as I recall from memory, but I'm not positive. May just be my imagination. But thats why I posted that question as a separate thread. Anyway, that's it and this time TI worked well for me just when I needed it. There are some issues that need to be dealt with but overall I am happy. I think someone less techinically inclined though would have had difficulty especially if they were unable to get networking to work. I also think that the documentation needs to be a little better and more detailed. Basic info is good but there needs to be a reference manual for details of operation such as what the image function actually does, what the check image function actually does and how it does it, etc.