Path: utzoo!utgpu!watmath!clyde!bellcore!rutgers!mailrus!ames!pasteur!ucbvax!RELAY.PROTEON.COM!acm From: acm@RELAY.PROTEON.COM Newsgroups: comp.protocols.tcp-ip.ibmpc Subject: Re: NCSA and KA9Q ?? Message-ID: <8812070233.AA18556@monk.proteon.com> Date: 6 Dec 88 21:28:00 GMT Sender: daemon@ucbvax.BERKELEY.EDU Organization: Proteon, Inc., Westborough, MA 01581 [(508)898-2800] Lines: 38 Steve, The newly announced Proteon p4100 router (or the p4200 router) with the IPX packet forwarder allows you to run tcp/ip or Novell (and under the correct driver revisions for Novell) to run concurrent Novell/TCP/IP packets throughout an internet. This gives you what I believe you are asking for. In addition you can run DECNET and XNS in the entire net if you have installed the approriate packet forwarders. The contact at Proteon is mcs@proteon.com (Mick Scully). He is much more knowlegable on it than I. -Al Marshall, Proteon ------------- This is in reply to Dave Crocker's note on Novell and IP. The problem we face is: Islands of Novell lans, TCP backbones, the Novell islands want to interoperate with each other. The Micom/Interlan product will not accomplish this. I caught the statement "That is, IP is encpasulated." in Mr. Crocker's reply. What I need to do is encpasulate the Novell IPX in TCP packets. That way, the Novell Islands could interoperate and use the TCP backbone to link. Is there any way to do this? The only idea I have is to purchase the asynch bridges from novell, connect then into the serial side of a TCP milking machine such as a 3Com(Bridge) CS/100 which could establish a telnet session. Then if we hold our mouths just right perhaps we would have a way of encapsulating IPX in TCP. Kludgy, expensive, to be sure. Novell lan<->asynch<->CS/100<->telnet<->CS/100<->asynch<->Novell lan What is the right way to solve this problem? Stephen Northcutt (snorthc@relay-nswc.navy.mil) (703) 663-7796