<?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 Set host via decnet over IP in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/set-host-via-decnet-over-ip/m-p/5096182#M88684</link>
    <description>We have a system that we do a set host from one node a to node b that takes 35-60 seconds to connect.  When we try the other way from b to a it's quick.  We are running DecNet over IP with TCPIP vers. 5.4 eco 6.  The systems are running OS 7.3-2.  I've tried flushing the ncl cache on both systems but it still takes along time to get to the username prompt the one direction.  Any help will be appreciated. TIA.  Mike</description>
    <pubDate>Wed, 05 Mar 2008 21:04:23 GMT</pubDate>
    <dc:creator>Michael LaRoche</dc:creator>
    <dc:date>2008-03-05T21:04:23Z</dc:date>
    <item>
      <title>Set host via decnet over IP</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/set-host-via-decnet-over-ip/m-p/5096182#M88684</link>
      <description>We have a system that we do a set host from one node a to node b that takes 35-60 seconds to connect.  When we try the other way from b to a it's quick.  We are running DecNet over IP with TCPIP vers. 5.4 eco 6.  The systems are running OS 7.3-2.  I've tried flushing the ncl cache on both systems but it still takes along time to get to the username prompt the one direction.  Any help will be appreciated. TIA.  Mike</description>
      <pubDate>Wed, 05 Mar 2008 21:04:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/set-host-via-decnet-over-ip/m-p/5096182#M88684</guid>
      <dc:creator>Michael LaRoche</dc:creator>
      <dc:date>2008-03-05T21:04:23Z</dc:date>
    </item>
    <item>
      <title>Re: Set host via decnet over IP</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/set-host-via-decnet-over-ip/m-p/5096183#M88685</link>
      <description>Michael,&lt;BR /&gt;&lt;BR /&gt;This sounds mightily like a DNS or Routing problem.&lt;BR /&gt;Could it be that, seen from the node where SET HOST lasts long, the first try to connect fails; waits for timeout; and then tries a second path, which responds?&lt;BR /&gt;Where the other direction, the irst try succeeds?&lt;BR /&gt;&lt;BR /&gt;hth&lt;BR /&gt;&lt;BR /&gt;Proost.&lt;BR /&gt;&lt;BR /&gt;Have one on me.&lt;BR /&gt;&lt;BR /&gt;jpe&lt;BR /&gt;</description>
      <pubDate>Wed, 05 Mar 2008 21:36:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/set-host-via-decnet-over-ip/m-p/5096183#M88685</guid>
      <dc:creator>Jan van den Ende</dc:creator>
      <dc:date>2008-03-05T21:36:11Z</dc:date>
    </item>
    <item>
      <title>Re: Set host via decnet over IP</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/set-host-via-decnet-over-ip/m-p/5096184#M88686</link>
      <description>These are usually either a back-translate error somewhere or some sort of a related a DNS or BIND delay, or a case where a less-than-optimal transport choice was selected via DECNET_REGISTER and you're seeing what amounts to a transport-level timeout, and a fallback.&lt;BR /&gt;&lt;BR /&gt;Try a numeric-address connect, too.</description>
      <pubDate>Wed, 05 Mar 2008 21:59:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/set-host-via-decnet-over-ip/m-p/5096184#M88686</guid>
      <dc:creator>Hoff</dc:creator>
      <dc:date>2008-03-05T21:59:11Z</dc:date>
    </item>
    <item>
      <title>Re: Set host via decnet over IP</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/set-host-via-decnet-over-ip/m-p/5096185#M88687</link>
      <description>Mike,&lt;BR /&gt;&lt;BR /&gt;As Hoff suggested from node a try a $set host ip$xxx.xxx.xxx.xxx to node b's tcpip address.  If this connects as fast as node b to a, then the problem is in name to address translation.  If this is still slow, try a telnet from node a to node b by address.  Try a telnet from node a to node b by hostname.&lt;BR /&gt;&lt;BR /&gt;If name resolution is slow, compare the appropriate NCL files on the two systems, probably NET$DNS_CLERK_STARTUP.NCL and NET$SEARCHPATH_STARTUP.NCL.  Does node a use an "off LAN" DECdns server by chance?  If so, have you configured node a to be able to find the off LAN server by running SYS$MANAGER:DNS$CONFIGURE.COM?&lt;BR /&gt;&lt;BR /&gt;Bill</description>
      <pubDate>Wed, 05 Mar 2008 22:30:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/set-host-via-decnet-over-ip/m-p/5096185#M88687</guid>
      <dc:creator>Bill Hall</dc:creator>
      <dc:date>2008-03-05T22:30:17Z</dc:date>
    </item>
    <item>
      <title>Re: Set host via decnet over IP</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/set-host-via-decnet-over-ip/m-p/5096186#M88688</link>
      <description>The solution was that the decnet address in the registry was pointing incorrectly.  Thanks for all the good advice.</description>
      <pubDate>Wed, 05 Mar 2008 23:37:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/set-host-via-decnet-over-ip/m-p/5096186#M88688</guid>
      <dc:creator>Michael LaRoche</dc:creator>
      <dc:date>2008-03-05T23:37:11Z</dc:date>
    </item>
  </channel>
</rss>

