NetNews Usenet Archive 1992 #20/NN_1992_20.iso/spool/comp/dcom/lans/misc/736

Internet Message Format | 1992-09-11 | 3.7 KB

Xref: sparky comp.dcom.lans.misc:736 comp.os.os2.networking:1311
Path: sparky!uunet!dziuxsolim.rutgers.edu!dorm.rutgers.edu!medici
From: [e-mail] (Mark Medici)
Newsgroups: comp.dcom.lans.misc,comp.os.os2.networking
Subject: Re: Lan Manager/Novell modem link?
Keywords: Microsoft Lan Manager Novell Netware modem argh
Message-ID: <[e-mail]>
Date: 11 Sep 92 23:06:36 GMT
References: <[e-mail]> <[e-mail]>
Followup-To: comp.dcom.lans.misc
Organization: Rutgers Univ., New Brunswick, N.J.
Lines: 61

[e-mail] (Dirk Rode) writes:

> I think, connecting two LANs via Modem is to slow to work on.

I generally agree, but it really depends on what kind of traffic will
transverse the dialup links.  Obviously, you would want to pull your
executable files off the local server (or local hard disk).  Also,
don't have any ideas about accessing database files accross the
dial-up, not unless you're using client-server technology.

> But what I know is that you will need a Router. This may be a dedicated
>PC running KA9Q, SLIP etc. You must connect such a PC to the
>existing LAN and to the Telephone net via Modem - or better -
>via ISDN. Its better to use ISDN because of the speed. In both
>cases an automatic dialup will be made when needed.

ISDN?  What's that (ha-ha-ha).

There's a couple of problems with this.  1st, as I understand it, ka9q
is an IP router.  Novell runs IPX/SPX while LanMan is, I believe,
NetBIOS based.  Worse, I seem to recall that NetBIOS is a non-routable
protocol.  However, you can tunnel (wrap) Novell packets in IP
packets, so ka9q (or any other dedicated router) can route them.  I
also believe that software exists to allow NetBIOS to tunnel in IP,
for the same effect.

However, a router is not your only option, or even best option.
Remote bridges will also work, and you won't have to worry about
tunnelling any protocols.  Some (most?) remote bridges have data
compression for the serial-line side, which might boost throughput, or
at least would allow you to use less-expensive modems.

The real problem is getting these two servers to talk to each other
or, more accurately, getting the client workstations on each side to
be able to access both the NetWare and LanMan servers.  I've read that
this is possible, but it doesn't look like fun and you don't have a
lot of memory available when you're done.

The question that immediately springs to mind is: Why do you want to
get these two networks talking?  Do you only want to exchange mail, or
do you need to access shared databases or collections of documents?
If the latter is your goal, don't underestimate the bandwidth of a
Federal Express Overnight Letter.

You can ship a Bernoulli cartridge, optical disk, or a QIC or DAT tape
with 90MB-4GB of data accross the country overnight for about $15.00,
which is probably going to be cheaper than the long-distance phone
charges, and you won't have to worry about making LanMan talk to
Novell or vica-versa.  Similarly, you can use dial-up links and timed
scripts to transfer updated files periodicly throughout the day,
without having to muddle through dual network protocol stacks on your
client workstations.

Your first chore needs to be to clearly define and express the purpose
for the link between networks.  Once you've done this, figuring out
the best way to achieve it will become easier.
--
_________________________________________________________________________
RUCS     | Mark A. Medici, Systems Programmer III, User Services Division
User     | Rutgers University Computing Services, New Brunswick, NJ 08903
Services | [[e-mail]]                    [908-932-2412]