Hi Michael,
I won't bore you with too detail, but Novell have a protocol and
ethernet packet type completely different from TCP/IP. In
addition they have the file storage system on Novell file servers
tightly coupled to the network protocol.
Because of this tight coupling, theoretically, to access a Novell
file server, the protocol suite is faster. The Novell client PC
has a sort of address, but this is dynamically allocated - that is
why you don't see an address for Novel PCs in any setups.
Although the Novell protocol is different, ethernet components
will work with both packet types - eg hubs and network cards. It
is possible and a regular practice to have both ethernet packet
types running thru the same ethernet components.
Most networking infrastructure (routers, bridges etc) vendors
support Novel's IPX.SPX protocol as well as TCP/IPand will happily
allow both protocols to route thru.
However, most organisation's policies will restrict protocols over
internal networks to TCP/IP only. To handle this, Novell supports
a system called IP tunnelling which allows Novell packets to be
carried inside a point-to-point TCP connection. It is possible,
and a regular practice, to connect users and servers together over
the Internet using tunnelling.
Many organisations with mixed servers and Internet requirements,
use a 'dual stack' on the PCs, allowing the PC to access a Novell
file server and TCP/IP-type systems - eg Internet, Unix hosts etc.
In your case, if you already have Novell file servers and expect
them to be around for a while, I would suggest that you (1) turn
netbios on on the clients and turn SAMBA on on the Linux box.
That way, the Linux box becomes a free file and print server. (2)
if TCP/IP is not already switched on on your clients, switch
TCP/IP on to access Unix-type services such as mail and intranet
web services on the Linux box. You can also have Novell 4.1x
servers running as web servers but it's messy.
If you set mail up right on the Linux box, gradually over time,
more and more users can be weaned onto access to internet and
internal mail & web services using their ordinary clients, getting
mail and web stuff from the outside world via a modem running ppp
on the linux box.
About the only thing Linux and SAMBA can't replicate is the
ability to easily manage users sharing multiple Novell 4.x
servers. This is because Novell have a handy system called the NDS
tree. This enables access permissions and passwords to be changed
once, then echoed across all servers that are relevent.
Hope this long note makes sense.
Kind regards
Tony Wells
Phenomenal Books
"I have made this letter longer than usual because I lack the
time to make it shorter" - Blaise Pascal.
[EMAIL PROTECTED]
bookstuff: www.phenomenal-books.com
anyotherstuff: [EMAIL PROTECTED]
Intnl tel/fax: +44 1524 845559
UK tel/fax: 01524845559
Mobile: (+44) (0) 370 963410
-----Original Message-----
From: Michael George <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Wednesday, June 24, 1998 12:42 PM
Subject: Novell & IP
>I'm working on getting a system running Linux this summer at our
local high
>school. I got some good pointers from the list about how to get
the system to
>interact with a Novell Netware server and to function as one.
I'm not worried
>yet about the servers, so I've saved that mail and will get back
to it.
>
>What I'm still unclear on is how Netware and IP interact... I
know that both
>run as a layer above the media protocol (ethernet in this case),
but I thought
>that Netware was the same layer as IP, and that one ran one *or*
the other.
>However looking at one of the PC's which still has Win'95 on it,
it seems to
>only have IP addresses. The Novell setup windows just seem to
point to
>servers.
>
>Also, all the info people send w.r.t. Novell was how to compile
in the IPX
>protocol and to use some packages (mars-nwe?) to setup and test
the server
>setup in Linux. However, there was no discussion of addressing
through
>Netware to the outside world.
>
>That leads me to suspect that rather than Netware being the
equivalent to
>TCP/IP, perhaps it is better the equivalent of NFS. This would
mean that all
>the PC's and the Linux box, all will have IP configured on them
and that they
>use Netware for file sharing. In this case, the Linux box should
pretty much
>sit on the net as normal and choose to play or not play with the
Netware
>servers and clients.
>
>I am interested in this, because if I have a small cluster of
Linux boxes,
>they can be on the net and dual-boot. When they are running
Linux, they can
>send traffic on the same ethernet that has Netware running on it,
but using
>TCP/IP and NFS. If my suspicions are right, there should be no
interference
>between Netware and the Linux stuff...
>
>If someone could take a brief moment to fill me in on the big
picture here,
>I'd really appreciate it.
>
>Thanks.
>
>-Michael
>
>--
>"They that can give up essential liberty to obtain a little
temporary
> safety deserve neither liberty nor safety."
> -- Benjamin Franklin, 1759
>
>
>--
> PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST
ARCHIVES!
>http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips
/mailing-lists
> To unsubscribe: mail [EMAIL PROTECTED] with
> "unsubscribe" as the Subject.
>
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject.
