QUOTE(ddustin @ Sep 5 2006, 06:18 PM)
I read and re-read your post and am amazed.
I think I get about 80% of it (this must be your line of work).
Sorry about that David.
I will try and restate some of this and keep it really simple.What is the 10 Connection Limit for Microsoft Workgroups?
If you are running a workgroup, Microsoft have intentially limited the TCP/IP stack (in C:\Windows\System32\Drivers\tcpip.sys) so that you cannot connect to more then 10 PC's at a time.
You can have more then 10 PC's in a workgroup, but if you try and connect to more then 10 PC's at the same time, you will get an Error 71 happenning and the extra connections will be blocked. So you might get away with a workgroup with more then 10PC's, but expect the occaisonal network communication failure.
If you use a Domain Server based network, Microsoft switch off this 10 connection limit.How Would this 10 Connection limit show up in a Netrender Workgroup?
Initially, everything might seem to be working with more than 10 slaves.
However, over time, I would expect to see Slaves disabled progressively by the Netrender Server due to communication errors. They would still show up as being "On-Line" in the lower window. Is there a really simple way of setting up a Domain Server system?
No.Can I get into serious trouble with a badly set up Domain Network?
Yes. Worst case, you could find youself shut out of every PC.If I get a Domain Server, it better be something Really Powerful. Right?
A Domain Server spends all its time doing absolutely nothing. It is just a manager and nothing more. For a network of, say, 50 PC's, even an old 100MHz Pentium I with 128MBytes of RAM would do fine. You just want something reliable.What is all this Virtual PC stuff?
It is much easier to try it then to read explanations. Go to www.vmware.com and download the free VMPlayer. Then go to their Appliance library and download one to try.
If you try it, it takes no time to understand it. You have a complete seperate PC running inside VMPlayer - seperate IP address, seperate everything. The complete virtual PC exists in one big file - called an "Appliance".Is there a good Reason to Consider using Virtual PC's?
Very good reasons, especially for something like a Domain server.
If a Domain Server dies, then the network dies.
So if if your Server PC starts spouting smoke and flames, what are you going to do.
If you are running a Domain Server on a VMWare virtual PC, that just copy the Appliance files to a DVD and it is backed up.
If you need to set up a replacement server, just install VMWare on a different PC. Copy the Appliance files. Run VMPlayer.
That is it!
Your server will be running exactly as it did before. Even if the new PC's hardware is totally different, it will have no effect on the running of the appliance.
There is no alternative that is simpler or faster.