I would prefer using ntfs-3g over the captive ntfs kernel module for write support. One thing you won't be able to do is fully repair a bad filesystem. The ntfsprogs package supplies an ntfsfix program. It will fix the most common problems and then mark the filesystem as dirty so that windows will scan the drive when you reboot into windows.
If the drive is connected to a windows machine and you share it, you don't need to configure anything in your smb.conf file. The smb.conf file is for the server. When you access a windows share, you will be using a client.
I find using konqueror is the most handy program for access smb shares. You can split the window and on one side enter the uri "smb://"
You can also mount a share.
mount -t cifs //hostname/sharename /mount/point -o rw,uid=yourusername,gid=yourgroup,fmask=117,dmask=007,username=windowusername,password=windowspassword
You can also add an entry to /etc/fstab. If you do, use the "credentials" option instead of username and password. Use the noauto option to prevent the system from hanging if the windows host isn't up, when booting up. I would also use the _netdev option. If you also add the "user" option, you can mount it without su'ing to root.
Please see the manpages for mount, fstab and smb.conf. I don't remember the exact name of the program that mount uses to mount cifs shares. cifs.mount or cifsmount or mount.cifs. Anyway, it will have its own man page as well.
I think I posted in the wrong window. Sorry.