<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: DEC LAT in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/dec-lat/m-p/3505670#M48899</link>
    <description>Hi Guys,&lt;BR /&gt;&lt;BR /&gt;I was afraid this was the case.  Thanks for your help.&lt;BR /&gt;&lt;BR /&gt;Steve</description>
    <pubDate>Thu, 17 Mar 2005 03:41:24 GMT</pubDate>
    <dc:creator>steve maher</dc:creator>
    <dc:date>2005-03-17T03:41:24Z</dc:date>
    <item>
      <title>DEC LAT</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/dec-lat/m-p/3505667#M48896</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I'm trying to analyse network traffic between a DEC repeater and a kilostream link without much luck.&lt;BR /&gt;&lt;BR /&gt;The current setup is like this&lt;BR /&gt;&lt;BR /&gt;DECSERVER 90m&lt;BR /&gt;     |            cat5&lt;BR /&gt;DECREPEATER&lt;BR /&gt;     |            cat5&lt;BR /&gt;DEC RouteAbout access E1&lt;BR /&gt;     |            x21&lt;BR /&gt;Kilsotream link&lt;BR /&gt;&lt;BR /&gt;If we put a hub between the routeabout and the repeater we can't seem to sniff all the traffic with ethereal.  All we get is a few spanning tree protocl messages (See attached, need ethereal to open).&lt;BR /&gt;&lt;BR /&gt;We need a decent trace in order to work out if we can replace the kilostream with ADSL.&lt;BR /&gt;&lt;BR /&gt;Any suggestions would be great on how to do this.&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;&lt;BR /&gt;Steve</description>
      <pubDate>Wed, 16 Mar 2005 04:34:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/dec-lat/m-p/3505667#M48896</guid>
      <dc:creator>steve maher</dc:creator>
      <dc:date>2005-03-16T04:34:56Z</dc:date>
    </item>
    <item>
      <title>Re: DEC LAT</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/dec-lat/m-p/3505668#M48897</link>
      <description>Ethereal doesn't support LAT capture and display.  If you're using LAT as the network transport you won't be able to replace this    circuit with an ADSL link, xDSL supports TCP/IP.  &lt;BR /&gt;&lt;BR /&gt;What you could do is bring up the xDSL link and migrate to TCP/IP protocols.  You'll need  TCP/IP (or the older UCX) on the VMS host.</description>
      <pubDate>Wed, 16 Mar 2005 12:58:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/dec-lat/m-p/3505668#M48897</guid>
      <dc:creator>Andy Bustamante</dc:creator>
      <dc:date>2005-03-16T12:58:48Z</dc:date>
    </item>
    <item>
      <title>Re: DEC LAT</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/dec-lat/m-p/3505669#M48898</link>
      <description>Steve,&lt;BR /&gt;&lt;BR /&gt;I don't use Etherpeek, but I would check the Routeabout documentation carefully. Some protcol bridging products will only transfer some of the protcols present on the Ethernet link.&lt;BR /&gt;&lt;BR /&gt;To be definitive, I would use a monitoring tool that captures bare packets (I carry around Etherpeek).&lt;BR /&gt;&lt;BR /&gt;Hope that the above is helpful.&lt;BR /&gt;&lt;BR /&gt;- Bob Gezelter, &lt;A href="http://www.rlgsc.com" target="_blank"&gt;http://www.rlgsc.com&lt;/A&gt;</description>
      <pubDate>Wed, 16 Mar 2005 15:55:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/dec-lat/m-p/3505669#M48898</guid>
      <dc:creator>Robert Gezelter</dc:creator>
      <dc:date>2005-03-16T15:55:02Z</dc:date>
    </item>
    <item>
      <title>Re: DEC LAT</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/dec-lat/m-p/3505670#M48899</link>
      <description>Hi Guys,&lt;BR /&gt;&lt;BR /&gt;I was afraid this was the case.  Thanks for your help.&lt;BR /&gt;&lt;BR /&gt;Steve</description>
      <pubDate>Thu, 17 Mar 2005 03:41:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/dec-lat/m-p/3505670#M48899</guid>
      <dc:creator>steve maher</dc:creator>
      <dc:date>2005-03-17T03:41:24Z</dc:date>
    </item>
    <item>
      <title>Re: DEC LAT</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/dec-lat/m-p/3505671#M48900</link>
      <description>LAT (Local Area Transport) is a broadcast protocol. It only operates on a local area network (Etherent/FDDI?). It is not routable. &lt;BR /&gt;&lt;BR /&gt;There use to be a device called a TRANSLAN that would extend a LAN accross a WAN,&lt;BR /&gt;&lt;BR /&gt;  Tim</description>
      <pubDate>Sun, 20 Mar 2005 18:33:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/dec-lat/m-p/3505671#M48900</guid>
      <dc:creator>Tim Hughes_3</dc:creator>
      <dc:date>2005-03-20T18:33:44Z</dc:date>
    </item>
  </channel>
</rss>

