Dear All,
I am pretty new to Helix acquisition - apologies in advance if this question looks really stupid.
I am trying to image a Mac Book pro using Helix3.0 bootable cd (by crossover cable)
1) I have booted the Mac with Helix 3.0 CD
2) Once it booted with Helix, I have configured a manual IP address (192.168.1.1)
3)Connected the forensic laptop with a crossover cable and configured the IP address of forensic laptop as 192.168.1.2
Now when I open linen and it comes with 4 tab i.e acquire, hash, server and quit - when I am trying to put it in server mode to sync with encase, it does not seems to be enabling the server mode - the tab seems to be disabled and highlighting the acquire tab.
Now my question is - Something wrong with the port/ IP/ or the cable? I have tried with another cable but its the same problem. I think I am missing something.
Any suggestion will be much appreciated.
Regards
A
Not an answer but a question (sorry) why are you using that particular method? If you don't want to/can't remove the source HDD then why chose the super slow cross-over cable acquisition? Is it last resort? Why not attach an external disk via USB or FireWire and use the Helix acquisition app rather than Linen, mounting the source drive as read only and the destination as read/write?
Thanks for your reply. I am doing a test, for linen. Thats the reason I am using this methodology. I am still suffering with this issue even using different cables….any suggestion will be helpful.
Regards
A
super slow cross-over cable acquisition?
Unless it is Gigabit Ethernet, then you can achieve good speeds. Have you tried a straight LinEn boot CD?
Thanks for your reply. I only want to test this exercise with Helix 3.0
Thanks for your reply. I only want to test this exercise with Helix 3.0
You've got a lot of restrictions to deal with. Is this a college exercise?
Hi Jonathan, No its a lab based (work related), nothing related to college or assignment. I wanted to compare the speed - thats the reason I was trying to acquire using Helix 3. I have done crossover cable acquisition quite a few times with Helix 2. But this is the first time I am trying using Helix 3. So just wondering if I am doing it right or is this a general issue with Helix 3.
Thanks
A
Ah, I see! The Helix 3 Pro support forum is now hosted by AccessData, perhaps it'd be worthwhile trying there? Good luck. http//forums.accessdata.com
Sent email to Access Data but no response yet .Please be advised that I am using Helix 3.0- I think this is different from Helix 3 PRO.
Sent email to Access Data but no response yet .Please be advised that I am using Helix 3.0- I think this is different from Helix 3 PRO.
It is - they are two different products.