Perhaps you have already the problem solved, but I'd like to say that there are always chances of data loss when manipulating partitions. There are many reason for this, like various hardware problems, defective connectors, power failure, power supply problems, and of course software bugs. That's why, we always recommend to take backup of any important content. It is better to work safely rather than trying to recover lost files. I remarked that professional users keep double or even multiple backup sets.
Furthermore, it is safer to run the system on a U.P.S., because a power loss can cause data loss or even brake an entire file system.
The way to proceed, in general, is to make some unallocated space adjacent to the partition to grow. If your "c" partition is the first of the hard drive (it is very usual), you need to shrink the second partition first. Shrinking a partition from the start point can take quite long time.
Sometimes, this second partition is a logical partition, i.e. located in another partition named extended partition. I don't know if this is usual for mswindows server 2003, anyway it was quite usual in many personal user installations. If this is the case, you need to shrink the extended partition too, to leave the unallocated space out. The GParted livecd shows the partitions and unallocated parts of the hard drive in graphical form.
The command
fdisk -lu
from the terminal window (linux command line) gives accurate info on the partition limits.
In a final step, you have to expand the first partition. In this case, you need to leave the start point of the partition with no change, and select no round at all in the G.U.I. of GParted.
It is usually recommended to use the latest stable version. There are help documents in the "Documentation" page, in the main GParted web page.
http://gparted.org/documentation.php
*** It is highly recommended to backup any important files before doing resize/move operations. ***