|I feel very kind of you taking so much inerest in my query and i dunno what on earth is not making you understand the exact what i am trying to express..|
My pleasure, that's why I'm here, to help whenever possible.
I'll tell you why I'm having a hard time understanding what you need. You're not explaining your situation very well. Every time I respond, you give me just a bit more information........LOL.
Had you explained that you actually do have a LAN with 1000 (or more) clients and you wish to be able to limit access to a server so as to not overload it, or the network, I wouldn't have had to ask a whole bunch of questions.
Now, knowing what you have for a network, and what you'd like to achieve, I have a better understanding of the whole picture.
First and foremost, unless the server itself has connection limiting software installed on it, or is behind a device that does the limiting, there is no way to limit the bandwidth of each connection to that server.
Second, in a large environment like this if you have the money, take a look at using multiple servers combined to "load balance" This would improve performance per connection, as well as allow you to allot more bandwidth per connection as the load would be shared across however many servers are in your load balancing farm.
No matter what, your server should have a hardware RAID and multiple disks in a RAID array that provides redundancey. RAID level 0 is the only one that doesn't provide redundancy but it does provide better performance when it comes to accessing data and doing reads/writes. I would recommend a RAID 10 (dual RAID 1's combined in a RAID 0) with a hotspare for each RAID 1.
Again, the server, or multiple servers setup to load balance, requires money. If you have the cash, spend it on good equipment and redundancy. If you don't have the budget then you're stuck making do and this makes things tougher. If this is your situation, look at bandwidth metering/limiting software that you could install on the server. Or, a hardware device you could put between the server and the rest of the network that would do the same job.
I have no experience with bittorrents so you would have to find a torrent forum or go to the software manufacturer for advice. Start by googling "bittorrent forum" to get some forums, like this one, that deal specificially with bittorrents.
I will tell you this though and you want to keep it in mind.
If you have 500 users all connected to one server downloading files and the server has no bandwidth limiting setup in place on the connections to itself, whether they're dragging and dropping the files directly through Windows Explorer, or using ftp, sftp, or torrents to do the actual file transfers, they will still be using the same amount of bandwidth per connection and be fighting each other.
You seem to have this idea that torrents will change that and they won't unless there's some way to do bandwidth limiting within torrents themselves....and as I said, I have no experience with them so don't know if they can.
The last thing I'm going to say on this is, if you find some decent software to install on your server that will limit bandwidth on a per connection basis, you will also want it to be able to limit the total number of connections. A network has a finite amount of bandwidth and once saturated, it's going to slow down for everybody. So, even if you limit the bandwidth per connection, if you don't also limit the maximum number of allowed connections at one time to no more than 80% of your network bandwidth total, then you could end up with your network, and server, having more connections than it can handle and again, everything slows down to a crawl.
It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.