According to MS - there is no limit. You're only limited by the amount of liscences you have & whatever your machine/network can handle. I would think a theoretical limit would be at the 65K limit for TCP addressing - but that's essentially "limitless"...
Obiously, a Gigabit ethernet Server can handle more connections than a 10Mbit network without adversely affecting performance.
FYI - if using RAS, there is a limit of 256 connections (because of 256 port-limit).
Thanks for the response. But does windows handle TCP/IP connections the same way for files (they both use handles)? I tried to open 1Meg file handles the same time but only crashed the program in the initialization phase.
Thats where it gets a little hairy, and depands on what you're using it for.
Here's some info on it I found on the Web...
Windows NT multiplexes all file requests to a single server over one virtual circuit. The SMB (Server Message Block) reserves 11 bits for the file handle, resulting in a maximum of 2048 file handles per connection.
If you're running Terminal Services - 2048 can easily be not enough with 200 clients using it. They'd be limited to only 10 open files.
Either way - trying to open multiple 1Meg files on a file server should be no problem. I dont think that is the issue with the program crashing. But - then again it all depends on what you're using.
I hope this was of some help for ya..
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.