Path: utzoo!utgpu!water!watmath!clyde!att!ucbvax!STC10.CTD.ORNL.GOV!cbb
From: cbb@STC10.CTD.ORNL.GOV ("CBB")
Newsgroups: comp.os.vms
Subject: "Tracing" LAT Connections ??
Message-ID: <8807110325.AA04367@ucbvax.Berkeley.EDU>
Date: 8 Jul 88 17:18:00 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: "CBB" 
Organization: The Internet
Lines: 19


	Someone must have solved this problem--
LAT Terminal Servers are great on a Broadcasting Ethernet cause you
can get non-DECnet'able machines on the network (connect em up via
one or more of the Servers terminal ports and establish a Service).

	Now, any node that can speak LAT, a Vax host, another LAT
Terminal Server etc., can establish a connection to that declared Service.
Great for Print Services, non-DECnet hosts etc.

	My Question--  How do you, or how can you "Trace" LAT connections?
I know that from a VAX host running LAT, you can get the Server and Port
that associated with a particular LTAx device in a least a couple of
different ways, BUT, how can one "Trace" a connection from some
arbitrary Server to another Server to learn which Ports/Services/Users
are involved??  This would appear to be a Security nuisance, especially
on a large LAN with a hundred LAT devices or so.
Anybody have a solution??
------