Converting my campus to an OSS p2p setup. Suggestions?

[annex]

Howdy,

This is just the background, skip this if you want
My university campus uses a program called 'RezX' for filesharing on our internal network (intranet). However the program seems to have rather poor support from the developers (if they even exist anymore) and it is very buggy on a number of machines, particularily Windows XP. In fact is only runs on Windows so I was a little ticked since I run pure Linux but I just dismissed it and decided to ignore the issue.

A friend of mine the other day was complaining about the RezX client always crashing on his and other people's computer and was rather determined to fix it. he asked me if there was anyway to "convert an EXE to code". I informed him that yes there are ways to decompile programs however since RezX is closed source if he decompiled and reused the code he'd likely be commiting and illegal act and would at the very least be shutdown. I informed him the much easier and far more ethical way would be to simply adapt an already existing opensource project instead. I mean why try to fix an awful piece of software when you can get a free one far easier?

He was a little hesitant because he has little background with OSS but in the end he seemed to understand what I was saying. Either way, I have no intention to let him try to replace the current system with one thats also proprietary so I'm currently trying to put my money where my mouth is and find a good OSS server and client which could replace RezX.

The meat of the matter
So, here's why I'm posting on the forums in the first place. What peer2peer configuration would you recommened for a university intranet? It does not need to, and in fact should not be accessible from outside the local network.

I thought OpenNAP with a good client would be ideal, what about you?

The OpenNAP server looks good but what would be a nice Win32 client to go along with it? Since the campus is almost pure windows it's important I find a good client which can be preconfigured so the user has to only install and go. If people have to configure their client I'm willing to bet a lot of them simply won't be able to, or will be willing to, even with a good guide. I'm betting thatt it'd be rather easy to preconfigure a client if it's OSS so that's not a huge worry.

So basically:

What protocol do you think would be best?
What client would you recommend that has win32 support?

Any advice etc. would be greatly appreciated.
Thanks,
- annex

[Oopsz]

Go with Gnutella. GnucleusLan works great for colleges, if your sysadmins aren't traffic shaping away all p2p activity, and you can set up a linux gnutella client to connect in. http://gnucleus.com/Gnucleus/general/download.html
_________________
Pop-before-SMTP with the Gentoo Virtual Mailhosting Guide