Slashdot Mirror


User: nairb

nairb's activity in the archive.

Stories
0
Comments
4
First seen
Last seen
Profile
(view on slashdot.org)

Comments · 4

  1. Re:Stupid question but what is a "directory servic on Novell Launches Anti-Win2k Campaign · · Score: 1

    NDS is the reason that Netware 4 was a flop, since it didn't work.

    BUT Netware 5 and NDS 8 are *extremely* stable (more than most on this forum would probably believe) --



    Anybody hope that Active Directory kills W2K? I mean I can draw some significant correlations between a Domain and a Bindery, and the issues that arise from migrating 100 or so binderys into a single tree.. ack!



  2. Re:Good luck, Novell on Novell Launches Anti-Win2k Campaign · · Score: 1

    Its worth mentioning that this isn't a NT vs. Netware FUD campagain.



    Its an Active Directory vs. Network Directory Services (notice the abscense of the word Novell) which is a directory platform which integrate and run natively all sorts of platforms including Solaris, HPUX, MVS, Netware, and even NT... (NOTE: Linux is about to ship, but it only runs on versions which support PAM.)



    Currently Active Directory only runs on NT, but apparently *nix ports are planned. I wonder if the Unix port will still require a reboot to make changes to the replication strategy? Seems they wouldn't let us Unix people have any reason not to run it on W2K, so they'll probably make us bounce the server just to save W2K face.



    bastards.







  3. Re:Stupid question but what is a "directory servic on Novell Launches Anti-Win2k Campaign · · Score: 2

    A directory service is very similar to NIS+ in the Unix world. It creates a central place for managing all user accounts.

    Though NDS is so far ahead of where NIS could ever be, specifically with regards to replacting the data, and sharing/exporting it into other formats such as LDAP.

    Its also important to mention that unlike Active Directory, NDS is *NOT* platform centric, it can operate perfectly fine on a network without any netware boxes.

    For example I operate a small e-commerce firm we have 3 Sun E250's and about 100 Linux boxes which run on Compaq proliants, we have *no* netware servers. But when I delete a user he disappears from all the systems, when I add a user I get to pick which groups (systems) he has access to. When he changes his password, the password changes on all the systems. Its a nice pretty java interface to manage the whole thing, its a bit slow under Linux but it runs well under CDE.

    NDS links into the PAM (Password Authentication Module) and really takes the headaches out of syncronizing passwords, etc.

    Right now we're just bringing up our Intranet webserver so all .htaccess logins are also authenicated against NDS. I hate having 26 different passwords on different systems. Did I mention NDS can also manage how many systems a person can be logged into?

    I know your wondering what happens if NDS goes down? (to be totally honest I have no clue, since it hasn't happened yet) but its supposed to read the local password file, we removed the root user and gave another "secret" user a root login, just enough access so I could reclaim the box if necessary, but NDS has been extremely reliable for us!

    I think we might have had more issues if we ran NDS on Netware since I think Netware is a poor excuse for an operating system. We're playing with the idea of running Netware for the marketing people so we can use ZenWorks to manage their workstations, Novell ZenWorks rocks, but it requires Netware.
    FYI: The linux verion of NDS isn't out yet, but i'm running the beta and it seems fine.

  4. Re:Stupid question but what is a "directory servic on Novell Launches Anti-Win2k Campaign · · Score: 5

    A directory service is very similar to NIS+ in the Unix world. It creates a central place for managing all user accounts. Though NDS is so far ahead of where NIS could ever be, specifically with regards to replacting the data, and sharing/exporting it into other formats such as LDAP. Its also important to mention that unlike Active Directory, NDS is *NOT* platform centric, it can operate perfectly fine on a network without any netware boxes. For example I operate a small e-commerce firm we have 3 Sun E250's and about 100 Linux boxes which run on Compaq proliants, we have *no* netware servers. But when I delete a user he disappears from all the systems, when I add a user I get to pick which groups (systems) he has access to. When he changes his password, the password changes on all the systems. Its a nice pretty java interface to manage the whole thing, its a bit slow under Linux but it runs well under CDE. NDS links into the PAM (Password Authentication Module) and really takes the headaches out of syncronizing passwords, etc. Right now we're just bringing up our Intranet webserver so all .htaccess logins are also authenicated against NDS. I hate having 26 different passwords on different systems. Did I mention NDS can also manage how many systems a person can be logged into? I know your wondering what happens if NDS goes down? (to be totally honest I have no clue, since it hasn't happened yet) but its supposed to read the local password file, we removed the root user and gave another "secret" user a root login, just enough access so I could reclaim the box if necessary, but NDS has been extremely reliable for us! I think we might have had more issues if we ran NDS on Netware since I think Netware is a poor excuse for an operating system. We're playing with the idea of running Netware for the marketing people so we can use ZenWorks to manage their workstations, Novell ZenWorks rocks, but it requires Netware. FYI: The linux verion of NDS isn't out yet, but i'm running the beta and it seems fine.