Explain why it might be taking so long to connect to a telnet or SSH
server (age-old DNS problem). Approved by: nik
This commit is contained in:
Dima Dorfman
parent
35998b81e8
commit
967ab6c797
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=9083
2 changed files with 90 additions and 2 deletions
|
|
@ -14,7 +14,7 @@
|
|||
|
||||
<corpauthor>The FreeBSD Documentation Project</corpauthor>
|
||||
|
||||
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.160 2001/03/27 23:48:03 dd Exp $</pubdate>
|
||||
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.161 2001/03/28 02:27:19 dd Exp $</pubdate>
|
||||
|
||||
<copyright>
|
||||
<year>1995</year>
|
||||
|
|
@ -4241,6 +4241,50 @@ IO range check 0x00 activate 0x01</screen>
|
|||
</itemizedlist>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question id="connection-delay">
|
||||
<para>Why does it take so long to connect to my computer via
|
||||
&man.ssh.1; or &man.telnet.1;?</para>
|
||||
</question>
|
||||
|
||||
<answer>
|
||||
<para>The symptom: there is a long delay between the time the TCP
|
||||
connection is established and the time when the client software
|
||||
asks for a password (or, in &man.telnet.1;'s case, when a login
|
||||
prompt appears).</para>
|
||||
|
||||
<para>The problem: more likely than not, the delay is caused by
|
||||
the server software trying to resolve the client's IP address
|
||||
into a hostname. Many servers, including the Telnet and SSH
|
||||
servers that come with FreeBSD, do this in order to, among
|
||||
other things, store the hostname in a log file for future
|
||||
reference by the administrator.</para>
|
||||
|
||||
<para>The remedy: if the problem occurs whenever you connect from
|
||||
your computer (the client) to any server, the problem is with
|
||||
the client; likewise, if the problem only occurs when someone
|
||||
connects to your computer (the server) the problem is with the
|
||||
server.</para>
|
||||
|
||||
<para>If the problem is with the client, the only remedy is to
|
||||
fix the DNS so the server can resolve it. If this is on a
|
||||
local network, consider it a server problem and keep reading;
|
||||
conversely, if this is on the global Internet, you will most
|
||||
likely need to contact your ISP and ask them to fix it for
|
||||
you.</para>
|
||||
|
||||
<para>If the problem is with the server, and this is on a local
|
||||
network, you need to configure the server to be able to resolve
|
||||
address-to-hostname queries for your local address range. See
|
||||
the &man.hosts.5; and &man.named.8; manual pages for more
|
||||
information. If this is on the global Internet, the problem
|
||||
may be that your server's resolver is not functioning
|
||||
correctly. To check, try to look up another host--say,
|
||||
<hostid>www.yahoo.com</hostid>. If it doesn't work, that's
|
||||
your problem.</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
</qandaset>
|
||||
</chapter>
|
||||
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@
|
|||
|
||||
<corpauthor>The FreeBSD Documentation Project</corpauthor>
|
||||
|
||||
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.160 2001/03/27 23:48:03 dd Exp $</pubdate>
|
||||
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.161 2001/03/28 02:27:19 dd Exp $</pubdate>
|
||||
|
||||
<copyright>
|
||||
<year>1995</year>
|
||||
|
|
@ -4241,6 +4241,50 @@ IO range check 0x00 activate 0x01</screen>
|
|||
</itemizedlist>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question id="connection-delay">
|
||||
<para>Why does it take so long to connect to my computer via
|
||||
&man.ssh.1; or &man.telnet.1;?</para>
|
||||
</question>
|
||||
|
||||
<answer>
|
||||
<para>The symptom: there is a long delay between the time the TCP
|
||||
connection is established and the time when the client software
|
||||
asks for a password (or, in &man.telnet.1;'s case, when a login
|
||||
prompt appears).</para>
|
||||
|
||||
<para>The problem: more likely than not, the delay is caused by
|
||||
the server software trying to resolve the client's IP address
|
||||
into a hostname. Many servers, including the Telnet and SSH
|
||||
servers that come with FreeBSD, do this in order to, among
|
||||
other things, store the hostname in a log file for future
|
||||
reference by the administrator.</para>
|
||||
|
||||
<para>The remedy: if the problem occurs whenever you connect from
|
||||
your computer (the client) to any server, the problem is with
|
||||
the client; likewise, if the problem only occurs when someone
|
||||
connects to your computer (the server) the problem is with the
|
||||
server.</para>
|
||||
|
||||
<para>If the problem is with the client, the only remedy is to
|
||||
fix the DNS so the server can resolve it. If this is on a
|
||||
local network, consider it a server problem and keep reading;
|
||||
conversely, if this is on the global Internet, you will most
|
||||
likely need to contact your ISP and ask them to fix it for
|
||||
you.</para>
|
||||
|
||||
<para>If the problem is with the server, and this is on a local
|
||||
network, you need to configure the server to be able to resolve
|
||||
address-to-hostname queries for your local address range. See
|
||||
the &man.hosts.5; and &man.named.8; manual pages for more
|
||||
information. If this is on the global Internet, the problem
|
||||
may be that your server's resolver is not functioning
|
||||
correctly. To check, try to look up another host--say,
|
||||
<hostid>www.yahoo.com</hostid>. If it doesn't work, that's
|
||||
your problem.</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
</qandaset>
|
||||
</chapter>
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue