Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!rutgers!ames!ucbcad!ucbvax!TAMVM1.BITNET!X230GV
From: X230GV@TAMVM1.BITNET.UUCP
Newsgroups: mod.computers.vax
Subject: VAX-IBM connections
Message-ID: <8702230052.AA29509@ucbvax.Berkeley.EDU>
Date: Sun, 22-Feb-87 18:40:24 EST
Article-I.D.: ucbvax.8702230052.AA29509
Posted: Sun Feb 22 18:40:24 1987
Date-Received: Mon, 23-Feb-87 05:36:01 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 16
Approved: info-vax@sri-kl.arpa

Regarding the query for linking VAXes to IBM machines: we have them connected
here using TCP/IP with equipment from Excelan on the VAX side and KNET
from Spartacus/Fibronics on the VM side.  After a few initial problems (which
Spartacus very quickly fixed), it works great; people on the VAX can print
using the Xerox printers attached to the IBMs, file transfer works well, etc.
although remote logins still have some glitches . . .
 
I can't tell you too much about the products myself, but the best sources
of info would probably be a couple of mailing lists . . . KNET-L@TAMVM1.Bitnet
for the KNET stuff, and WISCNET@TCSVM.Bitnet for Wiscnet, a public-domain
TCP/IP controller for IBM machines.
 
I know you requested DECnet interaction, and there is a package to get IBMs
to speak it, from Interlink --- but I'm really in the dark there!
 
---Glenn Vanderburg