egisin@watmath.UUCP (Eric Gisin) (11/02/84)
We have at least one set of Vaxes running 4.2 Unix and VMS on campus that would like to communicate through some network. My first thought was to get a Decnet implementation for 4.2 (because of the mysterious sys/netdecnet/* files in sys/conf), but recent articles have also mentioned tcp/ip for VMS. So, is Decnet protocol available for 4.2? Could someone comment on Decnet vs. tcp/ip as the choice of a common protocol between these systems? I'd like to use it to send print jobs from the Unix machine to the VMS machine (this is currently done over an async line with a simple protocol and no error checking), and remote file copy between the machines. We have a pair of DMF-32's to set up a syncronous link with (this also leads me to choose decnet), but we could probably get an additional DEUNA for the Unix system. Also, if one machine uses both protocols over the ethernet, does it require two ethernet controllers, or just modified software?
leon@mmm.UUCP (Leon Schilmoeller) (11/05/84)
I suggest you look into using TCP/IP to link 4.2 to VMS. WE
are using TCP/IP under VMS from The Wollongong Group (TWG),
which provides file transfer (FTP), virtual terminal/remote
login(telnet), and common mail delifery(SMTP) between 4.2
and VMS Mail. This package can share a DEUNA with DECNET
on the VMS side.
Contact the Wollongong Group
1135A San Antonio Rd
Palo Alto CA 94303-4374
(415) 962-9224
There is a similar package called FUSION from Network Research Inc
which also uses TCP/IP, so you may want to shop around.
Leon Schilmoeller
3M Company
St Paul, MN
leon@mmm