dcldd could be a good choice, included in Helix, the easiest way to get it work.
Main Topics
Browse All TopicsI have just started working with Encase 6.12. I was quite familiar with FTK but a little confused by the features of Encase. In FTK, it was quite simple to do imaging across the network. I have researched this procedure in Encase and it seems to involve a lot of side steps. My goal is to capture the network drive from another computer and image it onto my computer. Does anyone know a good way of doing this. Also, for anyone that uses this software in the industry, is it best to use a third party open source for this program instead of Encase for drive acquisition? Thanks!
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Assuming you are using Encase Forensic Edition 6.12 and not Encase Enterprise...
The vendor-approved method of doing an acquisition over the network is using a network boot CD, booting the system via that CD, and configuring the IP of the machine within the same range as your forensics workstation. Then firing up LinEn and doing the copy via a network cross-over cable. It is, most definitely, not an elegant setup. The reason for this is that Guidance Software sells a product called Encase Enterprise that is designed to be used for network acquisitions. As Encase Enterprise grew as a product, support for a "streamlined network acquisition" in Encase Forensic Edition kind of fell off.
Forensic Edition is primarily designed to have hard drives directly connected to your forensic workstation, either via directly connecting them to the motherboard or by using a USB to IDE/SATA adapter.
Currently, the method that I use when I need to do a network acquisition is to boot the target machine with a Helix CD. Helix is a/was an open-source forensically sound Linux distribution of various forensic tools, one of which is LinEn, which is the Linux Encase network copy utility. ( I say WAS because they recently went to also selling a pay-for version, but I think you can still download the free versions)
Since you are running 6.12, I figure you probably have access to the Encase User Manual which came with the product. Chapter 4 is devoted entirely to using and configuring Linen.
I wish I could tell you that there was an easier way, like an Encase provided boot disc, or some utility that came with Encase FE that you could run on the target machine, but this is the approved method.
I have used Helix before and it works quite well. For the project then, I think I am going to do both a demonstration of directly connected media as well as the LinEn methods. As the project is strictly limited to using the program itself (as its a Encase Demonstration Purely) that is what I will be limited to. However, for my own knowledge what is an alternative way to make a forensic disk image with any non Helix open source programs?
Helix has a slew of tools for making a disc image. Linen is just the unix utility that is made specifically to work with Encase. You could also use Helix (or any other linux live CD) and make a DD image of the drive, which would give you a bit-by-bit copy (assuming you used the proper flags at the command line). The thing that makes helix special vs. say, Knoppix, is that helix is designed for forensics, and as such usually mounts drives read-only from the beginning, where-as with other open source solutions, you have to make sure you mount the disks read only.
Encase, I believe, will allow you to import in a DD image. It didn't support this for a long long time, but they finally changed their mind around version 5 I believe.
The possible roadblock you could run into here from a legal standpoint is that you don't have any "proof" that the DD image is not corrupt or tampered with. Encase actually takes every 64K of data and does a CRC checksum on it before writing it to the encase image file, then it does an MD5 of the whole disk and compares it to the hash of the disk.
Heck if you aren't super worried about the legal issues, you could even use most of the open source hard drive cloning utilities like g4u or clonezilla or the trinity rescue CD.
Business Accounts
Answer for Membership
by: MalleusMaleficarumPosted on 2009-02-24 at 13:39:39ID: 23726892
When you say "network drive from another computer and image it onto my computer".
Does that mean Workstation A has the C: drive and a mapped network Z:drive and you want to image the Z: drive through the network onto your forensics workstation?
Or
Does that mean you want to image the C: drive of another workstation onto your forensics workstation via the network?