david@dcl-cs.UUCP (David Coffield) (07/05/85)
Can anyone feed me their experiences of running TCP/IP software on VMS. I know of several products that do this but I'm looking for particular users experience of such software. The sort of details I'd appreciate are things like - who distributes the software, how much is it, what's the documentation like, is it easy to use? Of particular interest would be information from those people running such software on an Ethernet LAN on which 4.2 BSD UNIX systems reside. I'd like to know how easy it actually is to get VMS and 4.2 to communicate by such methods. Thanks in advance, David. -- UUCP: ...!seismo!mcvax!ukc!icdoc!dcl-cs!david DARPA: david%lancs.comp@ucl-cs | Post: University of Lancaster, JANET: david@uk.ac.lancs.comp | Department of Computing, Phone: +44 524 65201 ext 4150 | Bailrigg, Lancaster, LA1 4YR, UK.
connolly@steinmetz.UUCP (C. Ian Connolly) (07/12/85)
> Can anyone feed me their experiences of running TCP/IP software on VMS.
My first suggestion is to avoid Gould's ACCESS software. We have had quite
a few problems with it, most notably in the realm of mail. After some small
number of messages, it dies and must be restarted.
We recently switched to Wollongong's software. Two of our vaxen (that I
know of) run just the networking software, some others run full Eunice,
and 1 vax (this one) runs Ultrix. We also have several suns and Lispms
on the same ethernet. Wollongong's stuff works well, but is expensive (on
the order of $10-20K). We can perform telnet, ftp, and smtp to just about
anything on the net (our Lispms barf on smtp). We *have* had problems setting
up one of our vaxen as an arpanet/ethernet gateway, though - it seems we
can have one, or the other, but not both. I'm not intimate with the details,
though. I suspect it's our problem, not Wollongong's.
--
C. Ian Connolly, WA2IFI - USENET: ...edison!steinmetz!connolly
, , ARPANET: connolly@ge-crd
An rud a bhionn, bionn.stpeters@steinmetz.UUCP (R L StPeters) (07/14/85)
>> Can anyone feed me their experiences of running TCP/IP software on VMS. > >We recently switched to Wollongong's software. Two of our vaxen (that I >know of) run just the networking software, some others run full Eunice, >and 1 vax (this one) runs Ultrix. We also have several suns and Lispms >on the same ethernet. Wollongong's stuff works well, but is expensive (on >the order of $10-20K). We can perform telnet, ftp, and smtp to just about >anything on the net (our Lispms barf on smtp). (Actually, neighbor Connolly, we have TWO vaxen running Ultrix.) With the full Eunice package, rcp, rlogin, and rsh also work well but do require a little awareness of VMS file types. I will respond to the original posting at length by mail on the many hours I've spent probing just how the Wollongong stuff works, particularly with regard to mail. >... We *have* had problems setting >up one of our vaxen as an arpanet/ethernet gateway, though - it seems we >can have one, or the other, but not both. I'm not intimate with the details, >though. I suspect it's our problem, not Wollongong's. The problem is not a technical one. Our Ethernet is not yet registered and may not be gatewayed to arpanet. We believe we can base a mail-only gateway on the Wollongong software by patching one of Wollongong's binaries. -- R. L. St.Peters (Dick) The "R" is for "Reptile". uucp: decvax!mcnc!ncsu!uvacs!edison!steinmetz!stpeters (uucp is forever) arpa: stpeters@ge-crd (federal express) "Any opinions expressed by my employer are probably not mine."