Newsgroups: bit.listserv.novell
Date:         Tue, 6 Oct 1992 12:13:17 EDT
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         "(Mark Medici)" <medici@DORM.RUTGERS.EDU>
Subject:      Re: Combining Two Networks - Recommendations

In bit.listserv.novell you write:
>I have two separate PC computer laboratories which are not connected to each
>other.  The distance between the two laboratories is approximately 75 feet.
>We want to start a project to combine both networks into one overall Novell
>network (implies new file server and Novell 3.11).  Here are the specifics
>of the two networks.

>                         LAB A                     LAB B

>  NOS              3COM LAN Manager 1.1      Novell 2.1, Rev a
>  Work-
>   Stations               16                         16
>  Printers                 3                          2

Assuming both labs use Ethernet of some variety, which is not clearly
expressed in your posting.

The simplest and perhaps most effective solution would be to run an
Ethernet between the two rooms.

Since you will have >30 devices connected to thin-Ethernet, it will be
necessary to split these labs into two networks if you are using thin-
coax Ethernet.  This can be accomplished via an external bridge or
router (either Novell's software running on a dedicated PC with two
network boards, or preferably a real bridge or router).  However, an
effective and inexpensive alternative would be to install a second
network interface in the server and have it handle IPX routing.  You
didn't mention any TCP/IP access requirement, so I won't dwell on con-
siderations therefor, other to say that there would be some additional
considerations required to address this.

I wouldn't expect very high network utilization out of a total of
32 clients.  However, if high network utilization is anticipated, you
may want to consider using two bus-mastering Ethernet NICs in the
fileserver (assuming the fileserver's bus will support this).

I would recommend setting-up the printers on dedicated printservers,
specificly devices such as Castelle's LANpress.  This will reduce the
load on your fileserver, and also overcomes the problem of long
printer cables and more printers than ports on the server.  You'd
really be surprised at how high printing drives the server utiliza-
tion.  Alternately, you can employ PC/AT class systems as dedicated
print servers, using either Novell's PSERVER.EXE or one of the many
excellent (and more reliable) alternatives.  I stongly advise you to
stay far away from Novell's RPRINTER--it doesn't work well at all.

NW3.11 is an excellent product.  However, unless you will need the
server to perform TCP/IP routing or support Macs, the 32 clients and
5 printers are well within NW2.2's capacity.

Things that you didn't mention, but should definately be considered,
are a tape backup device for the server (installed on a workstation,
or in the server itself) with good software, and a UPS to perform an
orderly shutdown of the server in the event of sudden power loss.
--
_________________________________________________________________________
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]