Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 240
  • Last Modified:

Microsoft Windows Versus Novell Netware 5.1

I would like to know what  netware has as equivalent of windows regarding the follwing items:

Windows Forest/Tree/Domains/OUs      what is the equivalent in Netware?

Windows: Global Group /Domain local group/universal group.   what is the equivalent in Netware?

what do I have to install in windows DC or member server or stand alone server  or windows workstation in order to communicate with netware server and vice-versa

  • 2
1 Solution
This Question is probably best-asked in the NetWare TA --> http://www.experts-exchange.com/Networking/Netware/
That said, and assuming that (in the case of the Novell products) you're talking about modern eDirectory and Open Enterprise Server (either the NetWare or Linux kernel version):

AD Forest - No equivalent because there is no need for one. AD has "forests" because AD lacks eDirectory's ability to Partition the Directory Services Tree. Remember, AD is really just NT v4.0 Domains, with transitive-trust and an extensible schema bolted on the side.

As a practical example, consider a company that has offices in New York and London, and a need for users to access resources in both (that is, the New York users need access to, say, a printer in London, and vice-versa). In AD, a DC cannot be a member of more that one Domain. So you'll have the London Domain and the New York Domain, because you don't want to shovel all that replication traffic across your WAN link when all people need is a printer (AD replicates entire objects, eDirectory merely replicates deltas). You then join the two into a Forest. When a user in New York wants to access the London resource, they must traverse the WAN link to authenticate.

With eDirectory, you Partition the Tree, and put a Replica of the London Partition on the New York server, and a Replica of the New York Partition on the London server. The New York user wanting to access the London resource now authenticates locally. They don't traverse the WAN link until they actually try to access/use the resource.

With eDirectory, you can add Partitions to/remove Partitions from servers at will - unlike AD, where to make a Member into a DC, or a DC into a Member, you basically have to re-install. In eDirectory, a server can hold multiple Partitions of a Tree, and with eDirectory v8.8 a server can even hold Partitions of different eDirectory Trees.

Tree - The main difference here is that AD is a flat, 2-D namespace. eDirectory is an actual 30-D, hierarchical database rooted in X.500 standards. AD is still basically NT v4.0 Domains - the management tools just make it look 3-D.

OU - In eDirectory, you can use OUs as a security principal (a method to assign Directory Service and/or filesystem rights). In eDirectory, an OU is actually a container object. In AD, its really just a leaf object that provides the illusion of hierarchy. Try creating a User ID "bob" in two different OUs in the same AD Tree. Can't do it. Since eDirectory really is 3-D, OUs are really separate containers.

Global/Domain/Universal Group - eDirectory merely has Groups, because membership size is not limited (it is in AD, which is why they invented that ugly hack called Nested Groups). A Group is a Group is a Group.

You might consider that limiting, but only if you overlook the fact that eDirectory offers a lot of other Object types for grouping other Objects: Organizational Roles and Profiles come to mind as two Object types that have no equivalent in AD.

Installation - Depends on what you mean by "Communicate".

If you mean simply to allow someone logged into the Windoze box to log into the NetWare (or OES) server, then all you need to do is install Novell Client 32.

If you want to make filesystems hosted on the NetWare (or OES) server available "natively" to a Windoze box, then you can use Native File Access Protocols on NetWare (or OES) to make the filesystems available via CIFS or NFS (could also do it over AFP, but you probably don't want that). NetWare and OES can also be iSCSI targets (and initiators, for that matter).

Note that as of NetWare v6.5 SP2, and all versions of OES, the OES (or NetWare) server can act as a Windoze DC. With the release of Samba 4, I'd expect that the next rev of OES will allow the OES server to act as an AD DC.

Featured Post


Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now