Hmm. Let's see.. Nearly all MS desktop apps limit things to 10 concurrent connections.. The 11th guy that wants to use the accounting software is just SOL, I suppose..
Yes, this is a fairly terrible article that misses a lot of key problems that make this a totally unacceptable solution for a real enterprise. Little details like password management or file management/locating seem to slip right on by, although I didn't read it in enough detail to relal find out. One thing, however - Anand is taking a stab at providing the Enterprise IT readers some interesting material that is of use.
Instead of being quite so critical, how about some constructive feedback? Not necessarily on THIS article, but what you'd like to see and some suggested topics... In fact, I'll start.
I'd suggest some articies on:
Managing a Windows Webserver - hardening, clustering, etc.
Layer 3+ switching
Proper DMZ/Internet border design
Enterprise networking on a shoestring - Good budget solutions for pressing business needs.
Alternate last mile solutions
Building and deploying GPO's with Windows 2000 Server
Managing Internet access and use
Structured cabling design
Enterprise AntiVirus bulding blocks
Of course, Enterprise is kind of a fuzzy word. How big is an Enterprise? (And no Captain Kirk jokes, please). 100? 500? 1000 users? All of these topics could be scaled way up or way down, depending on the number of users. For 100 people and a few servers you don't need a multi-gigabit Layer3 switched backbone.
Anyhow, my two cents. Yes, it's not a great article, but always try to be constructive!
- G