Xref: utzoo comp.os.vms:9198 comp.os.eunice:68
Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!rutgers!noao!tody
From: tody@noao.edu (Doug Tody X217)
Newsgroups: comp.os.vms,comp.os.eunice
Subject: Re: TCP for VMS/Eunice (help!)
Keywords: need support
Message-ID: <903@noao.UUCP>
Date: 7 Oct 88 05:23:28 GMT
References: <654@web.cme-durer.ARPA>
Organization: National Optical Astronomy Observatories, Tucson, AZ
Lines: 20

In article <654@web.cme-durer.ARPA>, paisley@cme-durer.ARPA (Scott Paisley) writes:
> We have a vax 785 running VMS 4.7 and Eunice 4.3.1.  This critter
> co-exists on our ethernet here with lots of suns and other ethernet
> type thingys.  We have recently had some problems with the Wollongon's
> implementation.  (mainly old bugs re-occurring in new releases, and
> lack of help at their end. - so I'm told by the people here who have
> delt with them.)  Our main problem as of late has been this.  When we
> telnet from our suns (OS - Unix) to the Vax (OS VMS) it works fine
> until you hit a cntl-c or cntl-y.  This will lock up the window on the
> sun completely!  This problem occurred after installing a new version
> of the Wollongon software.

The problem with telnet from a Sun to the VMS VAX is in the telnet program
distributed with SunOS 3.X - there is no flow control.  This is fixed
in SunOS 4.0, which includes the BSD4.3 telnet.  Another way around the
problem is to buy SunLink/DNI (DECNET) from Sun, and use the 'dnalogin'
(or whatever it is called) to login on the VAX.  The SunLink stuff has
problems of its own, though, and isn't available yet for SunOS 4.0.

	Doug Tody