From:	CRDGW2::CRDGW2::MRGATE::"SMTP::CRVAX.SRI.COM::RELAY-INFO-VAX" 19-OCT-1989 18:09
To:	MRGATE::"ARISIA::EVERHART"
Subj:	LAT Multicast Errors

Received: From UCBVAX.BERKELEY.EDU by GIZMO.SRI.COM with TCP; Thu, 19 OCT 89 10:08:53 PDT
Received: by ucbvax.Berkeley.EDU (5.61/1.39)
	id AA25670; Wed, 18 Oct 89 14:54:46 -0700
Received: from USENET by ucbvax.Berkeley.EDU with netnews
	for info-vax@kl.sri.com (info-vax@kl.sri.com)
	(contact usenet@ucbvax.Berkeley.EDU if you have questions)
Date: 18 Oct 89 17:27:33 GMT
From: ginosko!brutus.cs.uiuc.edu!wuarchive!wugate!berkley@husc6.harvard.edu  (Berkley Shands)
Organization: Washington University (St. Louis)
Subject: LAT Multicast Errors
Message-Id: <249@wugate.wustl.edu>
Sender: info-vax-request@kl.sri.com
To: info-vax@kl.sri.com


	Bug report for LAT under VMS V5.X (5.0 - 5.2)
It seems that VMS will transmit bogus LAT multicast packets that
kill 3rd party terminal servers. It also kills DEC terminal servers too.
You may see bogus (non-printing) characters in service names.
The trouble (as deduced by our LAN Analyzer) is service group field
corruption. INTERLAN and VISTA (datability) both have stop-gap patches
available for their products. They have provided them to us, and so far
they seem to work. The temporary fix (source unknown) is to add
a line "create service /id" just before "start node" in LTLOAD.COM,
then shut down LAT and restart it. I have not seen ULTRIX LAT having
this trouble, but then we only see 6 or 7 bad packets a day out of
60 machines... What a bugger to find!!!

	Berkley Shands
	Production Systems WG Chair,
	DECUS VAX Systems SIG Exec