Path: utzoo!attcan!uunet!shl!phil From: phil@shl.uucp (Phil Trubey) Newsgroups: comp.dcom.lans Subject: Re: SCO TCP/IP <-> Novell Netware/386 Message-ID: <1990Oct13.152838.19495@shl.uucp> Date: 13 Oct 90 15:28:38 GMT References: Organization: SHL Systemhouse Lines: 37 In article you write: >1. Is it okay to put the TCP/IP and Novell networks on the same >Ethernet cable? I know Ethernet packets is Ethernet packets, but will >Novell and/or ODT just ignore packets it doesn't understand? Yes. >2. If it's okay to do (1), then I suppose we could just use something >like PC-NFS plus NCSA Telnet on the PC's, right? It is usually very difficult to run multiple protocol stacks in a single PC with Novell. Novell has believe it or not *designed* their drivers so that they will be gauranteed not to work with any other resident protocol stack in the same PC. Presumably they do this so that they don't have to be worried about bizarre interoperability problems between their stack and anyone else's - if you can't do it, you can't find bugs in it. However, various more practical people have thought this restriction somewhat silly and hacked the Novell driver to allow it to work with other resident stacks. Most notibly there is a version of the Novell driver out there that will work with NCSA Telnet or FTP Software's PC-TCP Plus (which is FTP Software's version of NFS for PCs). I don't know if Sun's PC-NFS will work with this hacked Novell driver or if there is another Novell driver out there that works with it. I know that FTP will send you a copy of the modified Novell driver with their software if you ask for it. You probably can get it electronically somewhere too, but I don;t know where. >3. Again, if it's okay to do (1), are there versions of IPX and NETx >for SCO Unix? Not that I know of. -- Phil Trubey (UUCP: ...!uunet!shl!phil)