Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!husc6!bloom-beacon!mit-eddie!ll-xn!ames!amdahl!twg-ap!john From: john@twg-ap.UUCP (John Caughy) Newsgroups: comp.protocols.tcp-ip.ibmpc Subject: Re: Help with Netware compatible (hardware independent) pc-tcp/ip Summary: Help with Netware Compatiable pc tcp-ip Message-ID: <240@twg-ap.UUCP> Date: 28 Apr 88 16:49:51 GMT References: <8804221611.aa01260@Louie.UDEL.EDU> Organization: The Wollongong Group, Palo Alto, CA Lines: 35 In regard to the query of a topologically independent TCP/IP solution for Netbios networks, several solutions are available. Along with several different public domain implementations, Wollongong supports a Netbios interface for TCP/IP. When used in conjunction with a PC gateway, also available from Wollongong, PC LAN users can access Ethernet networks and their accompanying services utilizing TCP/IP protocols. The Netbios interface utilizes Netbios datagram service to transport TCP/IP packets over PC LANs. The gateway routes packets to Ethernet based TCP/IP backbones. The Netbios interface has been developed using the Novell Netbios and therefore should support any hardware interface also supported by Novell's Netware. The gateway requires a dedicated PC/AT to operate and supports up to three interfaces. The gateway supports a variety of Ethernet controllers as well token ring controllers and the Netbios Interface. Routes are established statically. Fragmentation and reassembly are also supported. Another possible solution would be to provide an interface to Novell's IPX layer. This solution would provide much better performance than the Netbios interface and maintain the hardware independence, however you would then be making a commitment to the use of the Novell product. I am unaware of any existing PC-IP interfaces to IPX, but its in the works here at Wollongong.