What does Novell's Netware do, exactly?

cleverhandle

Diamond Member
Dec 17, 2001
3,566
3
81
Like the title says....

Most of my networking experience is in Linux, and I can usually get the idea of all of those How-To's, even if I would never actually set up the service. But I don't really get how Netware fits in. Is it supposed to be some kind of OS-independent networking solution?
 

Jhereg

Senior member
Jan 23, 2000
260
0
0
Netware is basically like any other NOS, it offers file and print sharing.
What makes Netware desireable is NDS, Novell Directory Services.
This offers management of user identities, access privileges and other network resources.
NDS is base upon the X.500 Directory Standard ,as is MS Active Directory.
The difference is that NDS is much more mature than AD.
Netware software is server-centric, there is no desktop Netware OS , only client software.
 

ScottMac

Moderator<br>Networking<br>Elite member
Mar 19, 2001
5,471
2
0
As mentioned, Novell is a NETWORK Operating System, not a desktop operating system with a strap-on server process. It was build (from day one...almost twenty years ago) to be for network services exculsively. Because it was built from scratch to be a Network Operating System, it's optimized for network services, initially file service and printer service. The new version 6.something, also includes FTP, DHCP, DNS, WEB, Directory, proxy services....pretty much the whole banana.

What has always been the nice thing about Novell's NOS is that the client machine receives its services as if delivered by a server native to that environment. For example, A *NIX box thinks it's attaching to another *NIX box for NFS shares, a McIntosh thinks it's attaching to an Apple server (whatever they call it these days), Winderz has its own built-in client, or you can use the Novell's "Novell client for Windows," which offers some additional performance. All of these different protocol sets can be served out of ONE server. You can change virtually every configurable option on a Novell server WITHOUT HAVING TO REBOOT (includes hot-swap NICs, if the hardware supports it).

Also, since the NOS is dedicated to service, and optimized for service, a much smaller hardware platform can support a much larger client base faster then a comparable Windows box (usually several orders of magnitude). Like, a P3/500/512K Novell box will smoke a dual P3/gig/gig Windows server every day of the week. When Version 3 came out (a long time ago) Novell demonstrated it on the roll-out by hooking 1000 (one thousand) PCs to a single 386/33 server...every PC was pushing or getting data off the server....You'd be hard-pressed to find any "PC-Size" server (today) running NT, WIN2K, or XP that can do 500 concurrent sessions, let alone 1000. NTFS still sucks as a NOS file system...

Unfortunately, there are other issues. Not the least of which is that Novell has never had much of a marketing department. The spongy-headed IT/IS management that flocked to the MS bandwagon (because it's easier/cheaper to find GUIHead Rodent Ranchers than decent Novell Admins), and hosts of other depressing issues....Novell is superior to any MS server platform for nearly all typical functions. *NIX is still a better DB machine, IMHO, for anything/everything else...if it can be done in Novell or *NIX, either of those platforms will offer better reliability, better performance, better longivity than MS server platforms (maybe the Enterprise stuff is OK, but that's not the "typical" environment).


Anyway...that's my two cents worth. Now I'm depressed...

Scott
 

bozo1

Diamond Member
May 21, 2001
6,364
0
0
I agree 100% with ScottMac. My company made the switch from Netware to NT and I've been depressed ever since.

I routinely would have servers with 1500 clients connected, pounding on it, running a 120MHz Pentium with server rarely running above 20% utilization. Those days were sweet.