Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site brl-tgr.ARPA
Path: utzoo!decvax!genrad!panda!talcott!harvard!seismo!brl-tgr!ron
From: ron@brl-tgr.ARPA (Ron Natalie <ron>)
Newsgroups: net.lan
Subject: Re: TCP/IP for VMS wanted
Message-ID: <10850@brl-tgr.ARPA>
Date: Mon, 20-May-85 15:59:51 EDT
Article-I.D.: brl-tgr.10850
Posted: Mon May 20 15:59:51 1985
Date-Received: Tue, 21-May-85 01:50:35 EDT
References: <293@midas.UUCP>
Distribution: na
Organization: Ballistic Research Lab
Lines: 18


> I am just getting started in the net implementation business, 
> and am trying to get VMS and (4.2 BSD & System V) UN*X talking 
> to each other.  
> 
There are two VMS TCP/IP's that I know of.  The one is the DSI/Compion/Gould
ACCESS-T software, which we are running.  It sucks.  The other is the
Woolongong Group's TCP/IP which was taken from their UNIX under TCP product
and will run seperately.  It can't be any worse than the Compion.  It
seems to work passably, however, talking to Woolengong people convinces
me that they have no one there who really knows what's going on.

Of course, 4.2BSD comes speaking TCP/IP (pretty much) and there are a
couple of venders out now claiming TCP/IP in their version of System V.
Actually, AT&T has a contract to do TCP/IP for System V for the Army,
but they aren't compelled to do any work on it, and they are not.

-Ron