HDTenEightyP/NetNews huggingface dataset:
Newsgroups: bit.listserv.novell
Date:         Sun, 27 Sep 1992 10:17:20 EDT
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         Brett Warthen <BRETT@INFINITE.MHS.COMPUSERVE.COM>
Subject: Re: Protection from KNOCK.EXE

FORWARDED MESSAGE from "(Karthikeyan Gurnswamy)" (MAIL @ CSERVE
{INTERNET:jmfres11@UCS.USL.EDU}) at 9/26/92 10:47p
From: "(Karthikeyan Gurnswamy)" <jmfres11@UCS.USL.EDU>
Subject:      Re: Protection from KNOCK.EXE

Sorry - Changing the MAC address on the fly will not help you to get into
supervisor mode. The reason is - the client and server are state driven
that is maintains tables and numbers in NET3 (Please refer to old articles
on Netware Techincal Journals on 'Cracking the NET3' shell..) and just
rerouting packets to a new station will not work at all. (a) and (b) do
guarantee 100 % reliability !

Karthik
***** NOTES from Brett Warthen (BRETT @ INFINITE) at 9/27/92 9:46a
Not to belabor the point on this one, but...

The whole point of the recent talk of a security whole in NetWare (not
KNOCK.EXE, but the Dutch thing)...was a workstation generating an NCP
request that appeared to come from another workstation that was currently
logged into the network as Supervisor.

Don't think in terms of connection tables in the NETx shells...we're
dealing at a much lower level than this.  Nobody said it was easy to do,
but Novell has released a patch to address this "potential" problem.

------------------------+-------------------------------------------------
 Brett Warthen          |        MHS:  Brett @ Infinite (via NHUB/CSERVE)
 Infinite Technologies  | CompuServe:  >MHS:Brett@Infinite
 11433 Cronridge Drive  |   Internet:  Brett@Infinite.mhs.compuserve.com
 Suite H                |        FAX:  +1-410-363-3779
 Owings Mills, MD 21117 |       Fone:  +1-410-363-1097
------------------------+-------------------------------------------------
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-Envelope-to: NOVELL@SUVM.BITNET
X-VMS-To: IN%"NOVELL@SUVM.BITNET"
X-VMS-Cc: JRD
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Newsgroups: bit.listserv.novell
Date:         Mon, 28 Sep 1992 07:27:10 -0600
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         Joe Doupnik <JRD@USU.BITNET>
Subject:      Re: Need help with NACS/NASI 3.0

>
>I just installed an 8-port NACS on a Runtime 3.11 server.  Everything is
>working fine, and all of the NASIDIAG routines indicate everything is
>working (access, loopback tests, etc).
>
>I was under the impression that the NASI TSR would allow "dumb" communcation
>software to use the NACS, but there isn't anything in the manual about this.
>To make things worse, we don't have any NACS/NASI-aware communications
>software, so I'm as yet unable to actually use the NACS.
>Any ideas?
>Thanks,
>Chris
------------
        There are some commerical pgms supporting NASI/NACS and MS-DOS Kermit
does so too. I have only v2.x of NASI/NACS to develop against. In Kermit the
command is SET PORT NOVELL(NASI), abbreviated to SET PORT NOV.
        The NASI TSR, the client end of things, requires more sophistication
in a terminal emulator than you suppose; it has to speak NASI/NACS.
        Joe D.
Newsgroups: bit.listserv.novell
From: paul@ace.acadiau.ca (Paul Steele)
Subject: Security Breach Discovered!
Organization: Acadia University
Distribution: na
Date: Wed, 30 Sep 1992 17:01:19 GMT

I had quite a surprise this morning.  At 9:06:11 every user on one of our 
servers (invcluding me) received the following message:

"Security breach against station 12 neutralized."

This is the message which Novell latest security patch generates.  I was a 
little surprised to see it since I didn't think any of our students would 
find out quite this quickly about this newest way to break into Novell.  But 
as it turned out, I think there is a bug is Novell's patch.  It took me a 
little while to figure out who was on station 12 because the security NLM 
had dropped the connection.  I had to use PAUDIT to generate a list of 
logins/logouts (which turned out to be a VERY large file), but in the end I 
had located the user, and she was someone that works across the hall from me 
and had been using Pegasus Mail at the time of the incident.  She never 
recieved the broadcast message herself, but did get the message "Error 
receiving from server" as she tried to read a mail message and had to reboot.
Apparently the security NLM somehow thought that she was doing something
naughty when she actually wasn't.

This incident certainly doesn't give me a lot of faith about the 
effectiveness of this patch.


___
Paul Steele, Network Services Manager              902-542-2201x660
Acadia University, Computer Centre            FAX: 902-542-4364
Wolfville, Nova Scotia, Canada, B0P 1X0  Internet: Paul.Steele@acadiau.ca
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.novell
Date:         Thu, 1 Oct 1992 17:41:50 PDT
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         "({Darkavich})" <steve@WINTERMUTE.UCSD.EDU>
Subject:      Bootp Forwarding question

Here is a simple network diagram to demonstrate the behaviour of the bootpfwd
NLM.  If PC1 sends a bootp request out on the cable the packet goes to the
Novell server and is forwarded directly to the bootp server, like it
should.  If PC2 sends a bootp request the packet goes to the cisco
AND to the Novell server which then sends the packet directly to the bootp
server.  This results in the bootp server getting 2 bootp request from
any machine that lives on NET 1.  My question is this, can the bootpfwd.nlm
be setup so that it only listens to bootp packets from the interface on
NET1 and ignores the requests from NET2.  Because, this is a broadcast
protocal, the packets cann't be ignored, but I think the NLM can be
made to not forward requests from NET2.

Does anyone have any suggestons?  Brian?

Secondly, has anyone tried giving the broadcast address for NET2
as the IP address for the bootp server?  We have multiple backup servers
on our net and would like them all to get these forwarded requests,
not just one.


	  ---
	  | | PC1
	  ---
	   |
	   |
<--------------->  NET 1
	|
	|
       ---
       | | Novell 386 server
       --- acting as TCP router with bootpfwd loaded.
	|
	|
<-------------------------> NET2
    |		|
    |		|
   ---	       ---     		   ---
   | | PC2     | | Cisco Router    | | BOOTP SERVER
   ---	       ---     		   ---
		|	   	    |
		|		    |
<--------------------------------------> NET 3


Thanks,


	Steve Misrack
	steve@ucsd.edu
	UCSD Network Operations
	(619) 534-7485 voice
	(619) 534-1746 fax
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.novell
Date:         Wed, 30 Sep 1992 13:59:30 EDT
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         FUAD@ACAD.SUFFOLK.EDU
Subject:      backup devices

Hi Everyone!!

  We are in the process of looking into providing backup services for our
five servers on the network from a centralized location.  Is there a tape
drive (DAT) that can make itself available (such as laser printers with
network interface) to the servers for backup???  The backup procedures will
be done overnight (unattended).

thanks in advance....

Fuad@suffolk.edu
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.novell
Date:         Thu, 1 Oct 1992 13:35:45 HOE
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         Ramon Ros <ZCCBRRG@EB0UB012.BITNET>
Subject:      Routing on a 3.11 file server.

    It seems that whenever you install more than one lan boards on
different cabling systems, (in our case Token-ring and Ethernet), in
a file server, it becomes automatically a router. Is this true?
    In affirmative case, do you have any control on this routing? How
you can stop it?.

    Thanks in advance.

Ramon Ros. Universitat de Barcelona.
zccbrrg@eb0ub012.bitnet
From: ag129@cus.cam.ac.uk (Alasdair Grant)
Newsgroups: bit.listserv.novell
Subject: Re: IP Tunneling - max # servers? WHY?
Date: 4 Oct 92 19:38:15 GMT
Organization: U of Cambridge, England

In article <9210041451.AA15299@chaos.tci.com> Novell LAN Interest Group <NOVELL@SUVM.BITNET> writes:
>>  Don't you ever get cases
>> where some idiot starts spewing broadcast IPX packets all over the
>>campus, and doesn't restricting them to IP tunnels help to avoid this?
>
>The only recent problem I've had along those lines was when "some idiot"
>started spewing IP braodcasts all over the place......

Yeah, but that only hits performance, and with subnetting you can
help control it. And at least the protocol is well-defined. I'm talking
about when someone brings up a server, and another server across town
goes down, because they picked the same IPX network number. With IP
tunnelling you can create a nicely shielded group of servers without
any risk of being intruded on.

Of course, if Novell produced readily accessible technical documentation
of their networking protocol (to the level of IBM's SNA, or at least to
that of TCP/IP), there wouldn't be so much of a problem. The more one
has to guess, the more one wants to be protected from the dumb guesses
of other people.
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-Acknowledge-To: <074DEM@WITSVMA>
Newsgroups: bit.listserv.novell
Date:         Mon, 5 Oct 1992 17:50:20 RSA
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         Demetrius Christian <074DEM@WITSVMA.WITS.AC.ZA>
Subject:      Question with PS/2 95 and BusMaster T/R adapters

The original request was posted on 17 September. I'm only refferring
to it now since I had problems sending mail.

On 23 September Gail Chernosky replied to a question from owings@nwu.edu.
We have a PS/2 Mod 80 server running 2.15 REV C. Every so often the
workstation will loose their connections but everything seems ok at the
file server console with aprox 13% utilisation.

Gail apparently reported some timing problems with certain T/R adapter
micro-code revisions. I'd appreciate if Gail (or anybody for that matter)
could give me the micro-code levels that exhibits this problem.

Many thanx

--   ------------------------------------------------------------    --
| Demetrius Christian                  Tel:  (011) 716 8000           |
| Systems Programmer                   FAX:  (011) 339 1225           |
|                                      Page: 331 8101 Code 20832      |
| Computer Centre                            074dem@witsvma.wits.ac.za|
| University of the Witwatersrand, Johannesburg                       |
| P O WITS, 2050, SOUTH AFRICA                                        |
------------------------------------------------------------------------
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Organization: East Tennessee State University
Newsgroups: bit.listserv.novell
Date:         Tue, 29 Sep 1992 11:31:48 EDT
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         Eric Job <ERIC@ETSU.BITNET>
Subject:      Re: PC/TCP
              29 Sep 1992 08:16:09 AST from <justo@RMECE04.UPR.CLU.EDU>

On Tue, 29 Sep 1992 08:16:09 AST Justo Mayora said:
>I know this is an interest group on NOVELL but many of us
>have a network of PC and UNIX machines.
>I want to use HCL-eXceed (X-window server implementation for PC)
>on PC's in the network. The manual says I need to
>buy PC/TCP from FTP Software Inc. in order to use it.
>The company that sells PC/TCP says that there are three
>products related to TCP on the PC. One is PC/TCP that seems
>to have several applications included (telnet, rlogin, lpr, etc.)
>The other is called KERNEL and I don't know what it is but
>it seems like the TCP/IP drivers only. The other one is
>INTERDRIVE that I suppose is like NFS (Network File system).
>Does anyone have used these products? Could someone tell me
>which is the correct product to buy (PC/TCP or KERNEL) in order
>to use HCL-eXceed (the difference in price is about $110).

I believe the Kernel would be all you need (and HCL could confirm
this probably), but you might want the PC/TCP for DOS that
includes FTP, TELNET, etc. for debugging purposes (i.e. eXceed
does not connect, but if the TELNET does, then you know your
network is up, etc.).  You don't need Interdrive.  We use Novell,
FTP PC/TCP for DOS and HCL-eXceed here on many workstations quite
satisfactorily to connect to a VAX system (the PCs on token-ring,
the VAX on Ethernet, crossing an IP router).  Good luck.

Eric Job <ERIC@ETSU.BITNET>, (615)929-6857, BITNET TechRep
Network Administrator, Systems Support, Computer Services
Box 70,728, East Tennessee State University
Johnson City, TN  USA 37614-0728
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-Pmrqc:      1
Priority:     normal
X-Mailer:     Pegasus Mail v2.3 (R4).
Newsgroups: bit.listserv.novell
Date:         Thu, 1 Oct 1992 09:52:35 EDT
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         "Matt Piermarini" <MATT@BSS1.UMD.EDU>
Subject:      Unexpected SCSI Bus resets w/AHA-1740

I am hoping someone here might be able to give me a clue here since
Adaptec refuses to return any of my calls.   We have a 486-50 EISA
machine with the AHA-1740 EISA SCSI controller.  It has been running
for about 4-5 months with No problems.  One day, the fileserver
console (NW 3.11) was displaying "Unexpected SCSI bus reset" error
messages.  It turned out that 1 of our three 1.0 Gig External disks
was dead.  We removed the bad disk, but the Console message kept
appearing.  When this happened the file server could not write to the
volume and shut it down.  If I reboot the server, everything works
fine until the next "Unexpected message...".   I have tried 2
different 1740's, both with the same results.  The messages appear at
random intervals (from 1 hour to 3 days).  Any ideas????
Thanks,

+-------------------------------------------------------------+
|Matthew S. Piermarini                      MATT@bss1.umd.edu |
|College of Behavioral & Social Sciences    PIERMA@umdd.bitnet|
|Network Programmer                         301-405-1669      |
|University of Maryland, College Park                         |
|      That's not a bug, it's an undocumented feature!        |
+-------------------------------------------------------------+
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-VMS-To: IN%"novell@suvm.bitnet"
Newsgroups: bit.listserv.novell
Date:         Mon, 28 Sep 1992 14:25:00 -0400
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         MARK LAFONTAINE <MARK@NICKEL.LAURENTIAN.CA>
Subject:      Xircom & Packet Drivers

Greetings,

        Does anyone know if there is an updated packet driver available for
the Xircom Pocket Ethernet Adapter II. We have version 2.00 (920615) of the
drivers disk, and have been having problems with the packet driver PE2PD.COM

        Is there anything available from Clarkson ?

Mark Lafontaine
Laurentian University
Sudbury, Ontario, Canada.
From: MAILBOX@ZEUS.ICE.NL (Zeus Mailbox)
Newsgroups: bit.listserv.novell
Subject: odi driver(s)
Date: 5 Oct 92 10:36:28 GMT
Reply-To: mailbox@zeus.ice.nl
Organization: ETB-Lubbers Nederland B.V.
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-Mailer:     Pegasus Mail v2.3 (R3).

Dear Netters...

Does anyboby know if there are odi drivers for the following cards:
- 3com 3c507 (etherlink 16)
- Gateway Gether 8 bit

and where I can get them by ftp ??

Greetings...

Henno.



mailbox@zeus.ice.nl (Henno Keers)                     Zeus mailbox
---------------------------------------------------------------------
ETB Lubbers Nederland B.V.                            Nijmegen
Korenpad 1                                            6534 AS
Tel. +31 80 540111                                    The Netherlands
X-mailer: Pegasus Mail v2.3 (R1).
Newsgroups: bit.listserv.novell
Date:         Thu, 1 Oct 1992 10:34:24 EDT
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         *L/B'u <750610@CCLOA1.CCL.ITRI.ORG.TW>
Subject:      unsubscribe

unsubscribe NOVELL
 =-=-=-=-=-=-=-=-=-=-=-=-<< ITRI/CCL >>-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
   Chun-Yin Lin (Linda)                /     . ___   ___ /  ___
   Design Engineer                   /     / )   ) (   /  (   /
   Office Automation Dept. (D000)   (____ / /   / (___(  (___( (
   Computer & Communication Research Laboratories (CCL)
   Industrial Technology Rearch Institute (ITRI)
 --------------------------------------------------------------------
   E_mail Addr.   :  750610@ccloa1.ccl.itri.org.tw
   Delivery Addr. :  D000, Bldg. 14-187, 195 Sec. 4, Chung Hsing Rd.,
                     Chutung, Hsinchu, Taiwan 31015, R.O.C.
   Telephone      :  886-35-917537     Fax      :  886-35-944081
 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
From: medici@dorm.rutgers.edu (Mark Medici)
Newsgroups: bit.listserv.novell
Subject: Re: SMC disk 4.3
Date: 26 Sep 92 22:37:17 GMT
Organization: Rutgers Univ., New Brunswick, N.J.

kirchner@INFORMATIK.UNI-KL.DE writes:

>on dorm.rutgers.edu  I had found the file smcdsk43.exe, but this file
>is obviously corrupt. I ftp-ed both files smcdsk42 and -43 with one
>mget, the -42 is o.k., the -43 not.

Sorry,

I realized about a week ago that the -43 version was corrupt.  I fixed
it a few days ago, and you should not have any trouble now (I just
checked to make sure).

>Now I do not have any admin-address there.

You can send mail to me in regards to stuff in pub/novell.  Also,
mail to root@host should eventually get to the right person on most
any UNIX host.
-- 
_________________________________________________________________________
RUCS     | Mark A. Medici, Systems Programmer III, User Services Division
User     | Rutgers University Computing Services, New Brunswick, NJ 08903
Services | [medici@gandalf.rutgers.edu]                    [908-932-2412]
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-Envelope-to: NOVELL@SUVM.BITNET
X-VMS-To: IN%"NOVELL@SUVM.BITNET"
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Newsgroups: bit.listserv.novell
Date:         Wed, 30 Sep 1992 18:28:30 -0500
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         ACS_NETWORK@JMUVAX.BITNET
Subject:      Re: Need help with ODI packet and Zenith Z-note 386L

Jason,

I successfully used odipkt on a Znote several months ago. I didn't
have any problem with the standard load sequence which should be
as follows:

lsl
znote card driver (i don't remember the name)
odipkt
ipxodi
netx

Just add the odipkt statement between the Znote driver and ipxodi
statements in the autoexec.bat file that is shipped with the Znote.
If I remember correctly thats all I had to do.

Gary Flynn
James Madison University
From: CACHO@ITESO.BITNET
Newsgroups: bit.listserv.novell
Subject: Re: Error Receiving from network
Date: 5 Oct 92 19:30:55 GMT
Reply-To: Novell LAN Interest Group <NOVELL@SUVM.BITNET>
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-Mailer: ELM [version 2.3 PL11]
              "ubs1@ATTMAIL.COM"

>
> Approximately 2% of the packets on my networks have CRC's.
> After transmitting around 3 million packets I have had
> No ECB Available Count:                 18
> Send Packet Miscellaneous Errors:      330
> Send Packet Retry Count:               297
> Transmit Retry Failures:                33
> Number of resets to nic:                56
> Number of Carrier Sense lost Errors:   333
> Number of Interrupts fired by adapter: 241
>
> The first three counters are described in the SysAdmin manual,
> and I have a reasonable understanding of them, except:
> 1)  How high can these numbers be before they are a problem?

  in the case of Send Packet Retry Count:, it is a problem if
it begins to increase in ones increments, instead of 99 multiples
your number is 13 times 99, so i will say it's okay.
  When it begins this kind of behavior we unload the cards, load
them again, and everything is okay again.

> 2)  How can I find out what the Miscellaneous Errors are?
> The last four counters are not documented, that I can find
> and I would like to know what they are.
>
> - Aldon Hynes
> ubs1@ATTMAIL.COM
>


--
  Hector Gonzalez, Iteso University.
  Guadalajara, Mexico.
  Cacho@iteso
  Cacho@itesocci.gdl.iteso.mx
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.novell
Date:         Wed, 30 Sep 1992 21:26:40 BRA
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         Carlos Mendes <CARLOS@UFRJ.BITNET>
Subject:      Re: repeaters

The maximum number of repeaters between two stations in a Ethernet
segment is four. So, you have a maximum of 5 segments, connected
with 4 repeaters.
However, two of these 5 segments must not have any stations connected
to it. These segments are called "POINT-TO-POINT LINKS".
In the real life, the usual is to have a maximum of 2 repeaters, connecting
3 segments. But you can extend it to 4, if you use 2 "POINT-TO-POINT"
links.

When you introduce a router or a bridge, another Ethernet segment is
"created", and the above rules apply the same way to this "new" segment.
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-Envelope-to: NOVELL@SUVM.BITNET
X-VMS-To: IN%"NOVELL@SUVM.BITNET"
X-VMS-Cc: JRD
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Newsgroups: bit.listserv.novell
Date:         Tue, 29 Sep 1992 07:51:10 -0600
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         Joe Doupnik <JRD@USU.BITNET>
Subject:      Re: which is better IP tunneling or IPX routing?

>were about ready to install our second novell 3.11 file server on a
>primarily IP based campus internet. our end result will be two 50
>station token rings running IP and IPX. They will be joined at the
>router. The router can route IP and IPX protocols. My question is
>should we set up IP tunneling between the LAN's or should we let the
>router do the work? Or won't this scenerio work?
>
>I would appreciate being nudged in the "prefered" direction before
>I spend time diddling with both to see which I think is best.
>
>thanks!
>
>cs06999@montcolc         +***************************************+
>                         +                                       +
>Rick Morrow              +                                       +
>Montgomery College       +                                       +
>51 Mannakee St           +                                       +
>Rockville MD 20850       +                                       +
>(301)-251-7234           +***************************************+
---------------------
Rick,
        If your router will route IPX then by all means do so in preference
to IP tunneling. Tunneling repeats ALL adverts and trash, and it is much
slower than IPX routing. IPX routing is fast and lets you keep local adverts
(say printers etc) local. Users think the net is transparently connected in
both cases. You can easily run an experiment one quiet weekend.
        Joe D.
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Via: uk.ac.manchester.computer-science; Mon, 5 Oct 1992 15:26:09 +0100
X-Disclaimer: Any opinions expressed herein do not necessarily reflect
X-Disclaimer: those of Barclays Bank Plc.
Priority: normal
X-Mailer: Pegasus Mail v2.3 (R4).
Newsgroups: bit.listserv.novell
Date:         Mon, 5 Oct 1992 15:28:02 GMT
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         Rod Wilson <Rod.Wilson@BARCLAYS.CO.UK>
Subject:      Re: pserver

>     hi
>      we didn't used the PServer efficiently.we setup pserver in pconsole
>     then we tried to execute pserver but we get the folowing messages
>        there are no enough spx connection.
>       Secondly in our nw386 we have three group and we have three
>      laser printer.I want to connect one printer for each group.How
>       should describe these operations in login scripts ????
>
>        Yusuf  Kucuk
>       EASTERN MEDITERRANEAN UNIVERSITY
>        COMPUTER CENTER
> --------------------------------END OF QUOTED MATERIAL----------
>
Try putting 'SPX CONNECTIONS = 60' in the shell.cfg file on the
workstation running pserver. This should work.

Rod.Wilson@barclays.co.uk
Barclays Bank Plc
England
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU