Since everyone knows samba is a piece of crap anyway, I reverted to finally figuring out NFS, which turned out to be easier than I thought, with added features and *muscle flex*.
Lets get the easiest part done, enable NFS client for windows7.
Go to CONTROL PANEL, Programs and Feature, and select Turn Windows Features On or Off on the left hand side.
Find Services for NFS, and enable/check the Client for NFS box, and let it finish. That's it.
On Linux side, vim up /etc/exports
Assuming your linux machine is 192.168.2.100 (which in my case is true)...
I have a disk on /media/cdbackups/ for instance, which has a symlink on /mmm
So in my /etc/exports I have the following:
/mmm 192.168.2.56 192.168.2.75(rw,no_root_squash)
This enables 192.168.2.56 and .75 to access this NFS share (You could specify the whole network too). Note how much more convenient this is when compared to samba's 5000 flags for read/write/users. Do check the man pages for all options, I choice no_root_squash to make my lazy life easier).
Once you're done editing /etc/exports, run: exportfs -a
Now back on windows, mount it, anyway you want, the cmd prompt is the faster for me:
mount \\192.168.2.100/mmm t:Or, for some persistency:
net use t: 192.168.2.100:/mmm /persistent:yes
This simply mounts the share to drive T:
Do not forget your firewall on your nfs server. NFS/Portmap requires some ports to be open, like 111 and NFS's many ports :). Luckily FireHol makes this fun and fast, adding two lines should do the trick:
server nfs accept
server portmap accept
I have some 'dst' accepts on mine, to limit access, but the above plain and simple works.
That's about it.