Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!sdd.hp.com!think.com!hsdndev!cmcl2!acf3!chapman
From: chapman@acf3.NYU.EDU (Gary W. Chapman,WWH 318,212-998-3045,718-499-7815)
Newsgroups: comp.sys.novell
Subject: Re: Nos of Users
Message-ID: <23190005@acf3.NYU.EDU>
Date: 28 Jun 91 02:45:00 GMT
References: <2188@uqcspe.cs.uq.oz.au>
Sender: notes@cmcl2.nyu.edu (Notes Person)
Organization: New York University
Lines: 23
Nntp-Posting-Host: acf3.nyu.edu

100 = 100 simultaneous connections; this includes both users at workstations 
and devices like print servers which connect to the server.  You can have
lots more accounts.  But I think you would have a problem if you tried to have
more than 100 PCs all connect to the server (e.g. at boot time), even if 
everyone doesn't try to log in: a connection is established between a PC 
and server when the netware shell is loaded (usually at boot time).

  What I've never tried is this:  

  100 users log in, so no more can
  1 user logs out (so the server now describes that connection as
     "not logged in")
  1 user at a different pc turns his pc on, and an attempt is made to
     connect to the server (when NETx is run) and then log in.

  I am reasonably certain this will fail, as there are no open connection
  slots for this 101st person. Presumably, however, if this person who
  logged out would be so kind as to turn off his machine, then the server
  will eventually notice that the connection is no longer valid.

Could someone confirm this?  (No manuals handy!)

 - Gary Chapman, NYU