From: CRDGW2::CRDGW2::MRGATE::"SMTP::CRVAX.SRI.COM::RELAY-INFO-VAX" 20-AUG-1990 08:01:44.34 To: MRGATE::"ARISIA::EVERHART" CC: Subj: Thoughts On Current Problems With LAT And VMS 5.X... Received: by crdgw1.ge.com (5.57/GE 1.70) id AA27334; Mon, 20 Aug 90 06:22:30 EDT Received: From REMOTE.DCCS.UPENN.EDU by CRVAX.SRI.COM with TCP; Sun, 19 AUG 90 19:07:33 PDT Received: from XRT.UPENN.EDU by remote.dccs.upenn.edu id AA12076; Sun, 19 Aug 90 22:03:30 -0400 Message-Id: <9008200203.AA12076@remote.dccs.upenn.edu> Date: Sun, 19 Aug 90 22:06 EDT From: "Clayton, Paul D." Subject: Thoughts On Current Problems With LAT And VMS 5.X... To: INFO-VAX@SRI.COM, goldberg@davidsys.com X-Vms-To: @INFOVAX,IN%"goldberg@davidsys.com",CLAYTON Seeing Seth's message about LAT problems hit a chord with problems that we have been having also. The problem that we were having was on two of three VAX Cluster Consoles that were just upgraded to VMS 5.3-1, VCS 1.3, and DECWindows. Right after doing the upgrade, various people in the building tried to log into the systems (I have concluded most are hackers (excuse me, inquisitive end users ;-) )). The problem was that with VMS auditing enabled for various things, bells started going off about user break-in detection and it gave the username. The odd part was the 'break-in' was repeated several times in a row with MAYBE 300 micro seconds between them, thats .3 seconds. Knowing the people who had the various usernames being recorded were not touch typists, and that the system having the problem was a loaded VS3200 I started looking around. I have found two interesting items. 1. In the VAXCluster Console Software (VCS) release notes, put on during the installation, mention is made of a problem in the 5.3, 5.3-1 and 5.3-2 LTDRIVER.EXE image. It referenced a problem that started with addition of the code to handle the VT1000 X-windows terminal. The problem is flow control mucking up where it thinks it should be in the code. Patchs were given in the release notes for all three versions of VMS. The reference number for the patch in the VCS release notes is 'PATCH 4570'. 2. Going through DSIN for articles on LAT problems that I am having with DS100's, DS200's and VMS I came across an article that lists all sorts of problems with LAT for versions of VMS from 5.1 through 5.3-2. Queue problems, terminal connections and protocol problems were listed as problem and solution. The kit name is VMSLAT053 and supposedly works for all sorts of different versions of VMS to fix known problems. Mine is coming this week, so if things are not as they appear, I will write accordingly. The article was under the 'Terminal/Server' product entry in DSIN. If you are having LAT problems along these lines, I recommend a call to your CSC support center to get the fixes. Give them the above hints and it should cut down on the hunt time for the patches.... Have fun... pdc Paul D. Clayton Address - CLAYTON%XRT@RELAY.UPENN.EDU Disclaimer: All thoughts and statements here are my own and NOT those of my employer, and are also not based on, or contain, restricted information.