W2K Advanced Server Connections

[Tovian]

I'm new and I apologize if this question has been asked before. This may be long, but I want to provide as much information as I can. (I rarely get a good answer unless I ask a good question.)

I can make my way around computers - hardware/software, networking, etc., but I have almost no knowledge or experience with real servers and server OS's. I still don't want to play that game, but I have to research a connection problem for a client.

I'm working with a small business (about 25 employees). They need to store and access data on a central computer (within the same building). All the computers currently communicate with each other over an ethernet LAN. All the computers are members of a peer-to-peer (workgroup) network. That's all the sophistication this little company needs. For file storage they are currently using a network storage device (LaCie) that is running a mini Linux OS. "Running" is a poor description as this box can barely limp... access-times are atrocious and unacceptable. I need to improve this situation.

If Windows-XP did not have a "10 concurrent connection" limit I would implement the shared files on an XP machine. However, this limit precludes Vanilla XP. I also have a fully-licensed copy of the Windows-2000 Advanced Server OS. I am researching the possibilities of implementing this as a solution.

My questions are...

-If I install the W2K Advanced Server OS without it being a Domain-controller (no Active Directory and no other "server" capabilities) - just a peer-to-peer entity - will the OS still support "unlimited" (more than 10) concurrent connections JUST FOR SHARED FILES ?

-Will we still need to buy CALs so that all users (even though they are NOT logging onto a server) can access the common business files ?

I hope my questions make sense. We are simply trying to share files among 20-30 folks at the absolute least possible cost - but without software piracy or other "questionable" solution.

I do realize that a free Linux is an option - but we would rather keep everything as some flavor of Windows since none of the company employees is very knowledgeable about anything but Windows.

[blue]Thank You in Advance[/blue]

 

[gavm99]

HI,

If the server is installed using per seat connections then you will be fine. Each XP client has a built in CAL to access the server. There is no need to buy additional CAL's this scenario using Windows 2000 Server.

Thanks.



Gavin Moorhouse

http://www.lucidcomputersolutions.co.uk

 

[GrimR]

gavm99 I disagree. When did XP clients come with built in CALs? [I believe there was exchange 2003 and office that did that but never an OS that I know of]
You need a server license for each server within a Windows 2000 Server-based network and a Windows 2000 Server Client Access License (CAL) for each client computer that is used by an authenticated user or that uses Windows 2000 Server Services.

Server Services Requiring CALs

Client computers accessing the following server services in a Microsoft Windows 2000 Server-based network require Windows 2000 Server CALs:

* File services. Accessing or managing files or disk storage.
* Printing services. Printing to a printer managed by the product.
* Remote Access Service. Accessing the server from a remote location through a communications link, including a virtual private network.
* Terminal services. Using the terminal services feature of the server to enable client devices to use applications or data residing on the server

Tovian W2K Advanced Server is overkill. Why not buy Server with 2008 that way you up to date for the next 5+ years . Secondly you should look into seeing if a company had old server 2000 licenses and CALs and see if they are transferable. e.g I had 3 x 2000 server and 100 CALS [which did not have SA], and are not used any longer as I had to purchase 2003 R2.