More that 10 concurrent connections in a workgroup
As this question spans Windows XP, Vista and Windows 2003 and it's a "low level" query, I felt it appropriate to post in this section.
I support a small office network workgroup of a mixture of XP Pro and Vista. There's an XP file server and a separate print server (I'd like to get them combined) and I know of the 10 concurrent connections limit. I can foresee that we're going to need to exceed that soon, so I guess the simplest way is to go down the Windows 2003 route - but still in a workgroup. I don't have the luxury of school holidays when a significant part of the network can be modified. I have to do things "on the hop" whilst users are working, so configuring a domain is really out of the question at present.
1. What's the limit on the number of concurrent connections?
2. What's the distinction between concurrent connections and concurrent users? Is it simply the fact that a single client could be accessing the file server and print server simultaneously - is that one user and two connections?
3. I know there's the thorny issue of CALs to face. What's the approximate cost per CAL? Is it a standard rate or is there an benefit in buying "in bulk"? For instance, would a 100 CALs package be cheaper than 10 x 10 CALs? Would the example that I've given in (2) use 1 or 2 CALs? If the cost per CAL is standard, and it's cheap (£5), then it might be easy for me to convince the organisation, but if it's maybe £100 per CAL, that would be a different matter completely!
Sorry to have such noobish questions. I'm perfectly happy in the XP workgroup scenario and also with several domain issues from a theoretical point of view, but this could be my first real experience with Windows 2003 (other than my lab setup at home).