well if you want to access shares on the windows server, the best bet is using Samba on the linux workstation to access them. Alternatively, Win2k3 has microsoft's "Services For Unix" included(IIRC), which should let you access NFS shares on any *nix boxes on your network(with SFU's NFS Client), and also let you setup NFS shares on the windows box(with SFU's NFS server).
I briefly messed around with SFU(on XP) recently and didn't have much luck with it(admittedly I had no previous experience with SFU and was just bungling through it - however I seriously doubt the issues I had with it were the result of my ineptitude).
Using SFU, I got excellent transfer rates(same as I get now from a debian NFS server) pulling files from NFS shares on the XP box to my debian desktop, but before I could finish any
transfers, the windows box would always crash out and restart itself. The NFS client(from SFU) fared better, but only because using it did not result in XP crashing - transfer rates pulling from an NFS share on my debian desktop to the SFU box were simply pathetic - if I did the math right, about 3.5MB/sec. I never setup any samba shares on my linux desktop, but pulling files from the XP box through samba mounts, 4MB/sec is what I used to get, and about 6.0MB/sec using smb://share/address
to access the share in Konqueror(instead of mounts). By comparison, I see 10MB/s on basically every NFS transfer I do now that my fileserver is running linux.
There are a few commercial NFS products for windows which I suspect are all vastly superior to SFU, as those products won't be designed with ulterior motives (like trying to make people think SMB is a good product compared to NFS).
And there is Cygwin too, which I tried to try for use as a windows NFS server, but the Cygwin-specific install/setup script for NFS-server simply did not work and I did not have the patience to figure out why or to try to deducing everything the script did so i could do it manually. That said, I don't think
the script did much beyond creating 3 services.
To sum up, what I've learned in the last few months is that it's mostly not worth the effort trying to get windows to support unix services, and while transfer rates are terrible(in comparison), Samba is the best solution with the least headaches for accessing windows shares on linux and creating shares on linux that windows can access. In the end I decided it was more worth my time just replacing that XP install with debian and learning to go console only on my fileserver. But I'm just a geek rambling on about his home system(s), I have nobody else to satisfy but me, so Windows annihilation might not be in the cards for you.
If you want to remotely administrate this windows computer(from *nix), I recommend enabling remote desktop on the win2k3 box and using rdesktop
, at least if it's just on a LAN. I can't speak to what security measures might be needed using rdesktop over the internet (obviously an encryption tunnel...). rdesktop is great stuff though, and it's smoking fast over a LAN, faster IMHO than the M$ RDC.
Hope that helps.