Silicon Investor (SI) -- The First Internet Community

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? -- Ignore unavailable to you. Want to Upgrade?

To: Jack Whitley who wrote (21351)	3/23/1998 9:13:00 AM
From: Jim McCormack	Read Replies (1) \| Respond to of 42771

Native TCPIP will be a Problem for Novell Apps Just a quick note about native TCPIP..... It is not all upside on this new feature I hope everyone knows. Do you know why MS encapsulates Netbios? They did that so that all of the existing applications would still run. If they went to native TCPIP then all the existing apps using netbios would have to be changed and updated requiring the user installed base to upgrade them - major pain.... Novell Installations of 5.X will no doubt run both the native TCPIP stack and the older IPX/SPX stack - why because the apps you know and love require the IPX/SPX services and they have to be rewritten to go "Native" TCPIP. You will have to upgrade them etc.... major pain again. The current trend in networking is to move to fewer and fewer protocols. Novell is making a positive step and biting the bullet on the application transition requirements as they don't have to rewrite them the 3rd parties do.... I think they will be surprised at the lack of response by third party vendors to rewrite the apps to use the new services in place of ipx/spx. Good feature but over the short term it means two protocols stacks which is a negative IMHO. At any rate don't get too excited over native TCPIP just yet. I can't see anyone being able to implement a pure TCPIP network on Netware - You want to run applications don't you.... The press will feature this problem soon enough.... Jim McCormack

To: Jack Whitley who wrote (21351)	3/23/1998 9:15:00 AM
From: ToySoldier	Read Replies (2) \| Respond to of 42771

Jack, NetWare does not need NetWare 5 to be what you have mentioned. It already has a built-in IPX/IP router and countless organizations use this inherent feature of NetWare for just that purpose. In order to turn a NetWare server into a full functioning LAN/WAN router with full packet filter support, one must bolt-on the MPR software (Multi-protocol router). Because of NetWare's highly efficient kernel, the performance of NetWare as a router is comparable to many low/medium scaled hardware routers. It can also provide a form of switching since it can be treated as a bridge (and that is basically what a switch is). This new offering of native (all OSI layers) IP support for NetWare 5 has confused a lot of people. Because of this announcement of native IP support, many people believed that current versions of NetWare did not support the IP protocol at all - thats wrong. Even in NetWare 3.x has IP protocol and routing support, but the NCP (NetWare Core Protocol) that all external sources use to communicate with NetWare servers runs on IPX. With the addition of the NetWare/IP software, a company can wrap the NCP packets in IP instead of IPX. Although it removes IPX from the actual wire, it still is not native IP communication support (not to get anything confused - this is EXACTLY what NT server do now except that when they use the IP protocol they are wrapping the hugely inefficient NetBois inside instead of NCP. People call IPX chatty - anyone ever look at NT servers talking to the world? Not Pretty). In NetWare 5, what Novell is doing (and this is why it has taken so long for them to get NetWare 5 out the door) is actually replacing the key fundamental underpinning to NCP/IPX with native layers of TCP/IP. This means that the RIP/SAPing that we all know and hate must be replaced and that is not an easy task! But they have actually done it. I know for you non-techies this doesn't sound like a big deal, but this would be equivalent to converting your new car into a hover-craft (the wheels are different, the engine is different, the steering is different, etc.) and still making sure that it can be a car to those people that don't know how to drive a hover-craft! I have to give the Novell Engineers a lot of credit! So what does that mean to the industry? That means that NetWare 5 can run completely an internet protocol which makes it substantially more compatible to the internet than its competitors. I would be surprised if Microsoft converts their NT to full native TCP/IP support until after 2001! The ironic thing is that so many people think that NT has already got this level of support and that NetWare was the NOS that was far behind. In fact, its the other way around! Anyways, that my technical chat for the day - non-techies you can now open your eyes again. ToySoldier