<?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 long logon time in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/long-logon-time/m-p/6992866#M104174</link>
    <description>&lt;P&gt;Connecting to an Alpha with ssh to logon delays 62-65 seconds before the prompt "login as:" is appearing. No matter if it is from a PC client or another OpenVMS (V8.4/V8.4-2L1) system, the result is the same.&lt;/P&gt;&lt;P&gt;There are som exceptions where the response time is normal:&lt;/P&gt;&lt;P&gt;1) Logging in to itself, that is ssh nodeA from nodeA works as expected&lt;/P&gt;&lt;P&gt;2) First intent to login (after reboot?) with another parameter (nodename/short DNS-name, ip-address (number address), full DNS-name) works as expected, but repeated attempts takes 62-65 seconds before the prompt appears&lt;/P&gt;&lt;P&gt;Had a similar situation about 10 years ago, but cannot remember if it was on this machine or an Integrity server, nor do I remember how it was resolved.&lt;/P&gt;&lt;P&gt;This delayed is observed on an OpenVMS V8.3 UPDATE V12 and TCP/IP&amp;nbsp;Version V5.6 - ECO 4 system. TELNET is disabled, only SSH connections are allowed.&lt;/P&gt;</description>
    <pubDate>Fri, 05 Jan 2018 12:04:35 GMT</pubDate>
    <dc:creator>Bo Midberg</dc:creator>
    <dc:date>2018-01-05T12:04:35Z</dc:date>
    <item>
      <title>long logon time</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/long-logon-time/m-p/6992866#M104174</link>
      <description>&lt;P&gt;Connecting to an Alpha with ssh to logon delays 62-65 seconds before the prompt "login as:" is appearing. No matter if it is from a PC client or another OpenVMS (V8.4/V8.4-2L1) system, the result is the same.&lt;/P&gt;&lt;P&gt;There are som exceptions where the response time is normal:&lt;/P&gt;&lt;P&gt;1) Logging in to itself, that is ssh nodeA from nodeA works as expected&lt;/P&gt;&lt;P&gt;2) First intent to login (after reboot?) with another parameter (nodename/short DNS-name, ip-address (number address), full DNS-name) works as expected, but repeated attempts takes 62-65 seconds before the prompt appears&lt;/P&gt;&lt;P&gt;Had a similar situation about 10 years ago, but cannot remember if it was on this machine or an Integrity server, nor do I remember how it was resolved.&lt;/P&gt;&lt;P&gt;This delayed is observed on an OpenVMS V8.3 UPDATE V12 and TCP/IP&amp;nbsp;Version V5.6 - ECO 4 system. TELNET is disabled, only SSH connections are allowed.&lt;/P&gt;</description>
      <pubDate>Fri, 05 Jan 2018 12:04:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/long-logon-time/m-p/6992866#M104174</guid>
      <dc:creator>Bo Midberg</dc:creator>
      <dc:date>2018-01-05T12:04:35Z</dc:date>
    </item>
    <item>
      <title>Re: long logon time</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/long-logon-time/m-p/6992941#M104175</link>
      <description>&lt;P&gt;&amp;gt; Connecting to an Alpha with ssh to logon delays 62-65 seconds before&lt;BR /&gt;&amp;gt; the prompt "login as:" is appearing. [...]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp; The usual explanation of login delays is a (slow) failure in a DNS&lt;BR /&gt;address-to-name (reverse) look-up.&amp;nbsp; The test is a command like:&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; nslookup &amp;lt;client_IP_address&amp;gt;&lt;BR /&gt;on the _server_ (after you get logged in).&lt;BR /&gt;&lt;BR /&gt;&amp;gt; 1) Logging in to itself, that is ssh nodeA from nodeA works as&lt;BR /&gt;&amp;gt; expected&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp; If the name+address is in the local data base, then a DNS problem&lt;BR /&gt;might not matter.&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp; Note that specifying the server's IP address instead of its name does&lt;BR /&gt;not help.&amp;nbsp; The problem is on the server side, trying to get the client's&lt;BR /&gt;name.&lt;/P&gt;</description>
      <pubDate>Fri, 05 Jan 2018 17:38:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/long-logon-time/m-p/6992941#M104175</guid>
      <dc:creator>Steven Schweda</dc:creator>
      <dc:date>2018-01-05T17:38:26Z</dc:date>
    </item>
    <item>
      <title>Re: long logon time</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/long-logon-time/m-p/6993100#M104178</link>
      <description>&lt;P&gt;That is, the name servers where all old, and not in use. Alas, replaced those with the current ones, and also changed the domain name&amp;nbsp; as it was not the same as on the other servers.&lt;/P&gt;&lt;P&gt;Anyhow, the connection was still slow, but after rebooting the server the response time was normal.&lt;/P&gt;&lt;P&gt;Thank you very much.&lt;/P&gt;</description>
      <pubDate>Mon, 08 Jan 2018 13:02:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/long-logon-time/m-p/6993100#M104178</guid>
      <dc:creator>Bo Midberg</dc:creator>
      <dc:date>2018-01-08T13:02:52Z</dc:date>
    </item>
  </channel>
</rss>

