Novell (NOVL) dirt cheap, good buy? Message Board

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : Novell (NOVL) dirt cheap, good buy?

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next

To: PJ Strifas who wrote (29040)	11/20/1999 2:01:00 PM
From: ToySoldier	Read Replies (2) of 42771

PJ/Scott/Others... One thing I have been waiting for from Novell and I have not seen any real sign of yet is a revolutionary thin client. I am not exactly sure how this would be developed but it would have to have the following: 1) All the required and optional functions that the current Novell 32bit Win9x/NT client has (i.e. full NDS tree authenitication and security, ZENworks, NDPS, etc.) 2) Ability to provide transparent access to NT domains and the resources of NT servers (i.e. file/print) that have been pulled into the NDS via NDSforNT. Example: be able to map a drive from a NetWare server and an NT server. 3) Universal client resource access regardless of client. In other words, access to these resources & services regardless of my location or the actual client portal I enter from. 4) THIN code that is memory resident and optional client demanded code pulled in when demanded by the service. In other words, some form of a full suite of client services in the form of pointers/hooks that the pull in the actual code when the servers requires it. I am not exactly sure how this would be accomplished, but I have seen a need for such a revolutionary client and it has not appeared on the horizon with Novell yet. I would think that it would be addressed via a browser and complicated Java Appletes, Beans, etc. Some of the optional appletes/beans may be pushed from the network/tree just prior ro being executed at the client, instead of having them all pre-stored on the client's hard drive. I criticism that keeps coming up in real life Novell/MSFT enterprise clashes is how HUGE the Novell client has become, how complex the 32bit client has become, how bug ridden it constantly is, and how non-integrated the client is to non-Novell OSes. One good example... We have a large enterprise financial customer that has recently acquired another larger financial entity. Company 1 is Novell centric and Company 2 is MSFT centric. The clients on each of these companies wants to seemlessly access the resources of the other company's servers. The Novell 32bit client provides a lot of enhanced functionality but does not transparently provide access to the NT server resources (i.e. map a drive to these servers). The NT client code does not recognize NetWare server resources unless a dual client config is set up. The NT gateway server for NetWare was setup but is not designed for large NT-NetWare integration. If Novell had a revolutionary client that met the above requirements then both companies could install the universal client and access all the resources of both companies. It would also go a long way to dispell MSFT battle to remove Novell's technology because the answer on the client battle is currently a MSFT or NOVL client line in the sand. What are the comments and ideas or insights from all of you on this issue. Toy

Report TOU Violation

Share This Post

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next