Re: Maximum Number of Clients

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: no one (anonymous_at_discussions.microsoft.com)
Date: 05/13/04 

Date: Thu, 13 May 2004 13:48:30 -0700

You ought to put the server software on that machine. 14
boxes constitutes a client/server environment. You might
as well get the benefits that "server" will give you in
that network over "pro".
>-----Original Message-----
>See below.
>
>
>"Kaye" <anonymous@discussions.microsoft.com> wrote in
message
>news:c63a01c438b4$88b4b730$a001280a@phx.gbl...
>> Recently, I updated a Windows 98 peer-to-peer network
to
>> Windows 2000 Professional. Although this a peer-to-peer
>> network, one "workstation" is beefed up with RAID, Hot-
>> Swap power supllies and Daily Backups and is set aside
as
>> a "server" with all data files stored on it and no user
>> using it as a workstation during normal operation. Here
>> are my questions:
>>
>> 1. While these 14 computers running under Win98SE
didn't
>> encounter and "Maximum Number of Clients Exceeded"
>> problems; Windows 2000 balks at allowing 13 computers
>> connect to one. I am running a DOS program that
requires
>> drive mapping. Is there a way to modify the Registry so
>> one can exceed the 10 connections limit or is it hard
>> coded?
>It's hard coded. You need to buy a Server product (which
>you should anyway, given the number of workstations you
>have).
>
>> 2. Each of the workstations may have 4 to 5 different
>> users during the day. How can I setup "Drive Mapping"
for
>> one user and replicate it to the other users instead of
>> having to enter it for each user?
>
>Use a logon script. Place it into a universally
accessible
>folder on your "server", then use a batch file on each
>workstation to execute the central batch file. On
>the workstations, the batch file must reside in the
>Startup folder.
>
>On "real" servers, you perform this task centrally via
>the domain logon script.
>
>
>.
>

Relevant Pages