Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!wuarchive!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!pacbell.com!tandem!netcom!jbreeden
From: jbreeden@netcom.COM (John Breeden)
Newsgroups: comp.dcom.lans
Subject: Re: Novell 3.11 with TCP/IP
Message-ID: <25188@netcom.COM>
Date: 22 Feb 91 17:25:07 GMT
References: <499@elroy>
Organization: Netcom - Somewhere in the S.F. Bay Area
Lines: 26

In article <499@elroy> marka@dsinet (Mark Anacker) writes:
>Hi,
>  In a recent issue of Network World, there was an announcement that the
>latest version of NetWare 386 (3.11) will have full TCP/IP support,
>including NFS to the server.  We are in the process of designing a 50-node
>or so PC network into our existing TCP/IP Unix net, so this news was
>greeted with a great deal of excitement (and a generous portion of
>skepticism).
>

The only "gotcha" I've seen so far is with the NFS part. It seems you can
NFS mount a Netware volume onto a Unix box but you cannot NFS mount a Unix
filesystem onto the Netware box (ie: I can mount Netware onto my Sun, but I
can't mount my Sun onto the Netware server and make it available to my Net-
ware PCs).

The other question is: If I implement 3.11's "IPX encapsulated in TCP-IP",
do I have to mantain the TCP-IP/IPX routing tables by hand?

-- 
 John Robert Breeden, 
    jbreeden@netcom.com, apple!netcom!jbreeden, ATTMAIL:!jbreeden
 -------------------------------------------------------------------
 "The nice thing about standards is that you have so many to choose 
  from. If you don't like any of them, you just wait for next year's 
  model."