Generally, imaging a hard drive means to create a faithful bit-copy of the device, including the boot sector (boot loader and partition table). This requires physical access to the device - you CANNOT do this over a network! If you are considering two systems connected via a network interface, then both systems have to be running, and there has to be some software on the target end (the system you want to image) that will present the device to another on the network. Typically this is via a file system manager, such as Samba, NFS, Andrew, etc.
So, if I were grading your teacher of this class, I would fail them if you have presented your assignment correctly. What I would do is to get an external drive enclosure, remove the Linux drive, install it in the enclosure, connect to Windows, and then use available software to copy the entire physical disc to a compressed file on the Windows hard drive. However, this is usually reverse of what one needs to do in the real world - generally we use Linux systems for forensic analysis of both Windows and Linux systems since the tools are much more powerful, less prone to compromise, and robust for this sort of work. I speak as a professional systems software engineer with 30 years experience in the field.
BTW, mfillpot's suggestion is a good one, with one caveat - this will result in a view of a running system. This can be good, but in any case you want to get the following:
1. A raw disc image dump of the system drive. This will get all files, boot loader, partition table, swap space if on same disc (usually is).
2. A complete memory (RAM) dump.
3. A raw disc image dump of any other drives attached to the system.
As I said, you will have to run software on the target system, which will skew the results since the software required to capture the images will affect those images, especially the memory and swap space dump. The disc image dumps are best captured from a shut-down system. The memory dump requires that the system be running. However, to be complete, you should get disc image dumps from both the running system, as well as when it is shut down. Some system compromises can mask themselves when the system is shut down, and if installed into the kernel can also mask themselves when the system is running as in "oh, someone has mapped RAM and is copying it - I'll remove myself to elsewhere until they are done...". Anyway, good luck with your endeavors in the realm of computer forensic analysis.