Hi,
I'm actually still have some problems with these slow-to-establish
network connections. On our network of three Linux Red Hat 6.0
machines, two of them are working fine. I can telnet and ftp between
these two without delay now. The third machine, jonesy, is still having
problems, both trying to reach out to other machines and having other
machines connect to it. On jonesy, I can telnet to 127.0.0.1 and
localhost just fine, but if I try to telnet to jonesy or its local
static IP address, it take about a minute to establish the connection.
If I try to connect to another machine from jonesy, or try to connect to
jonesy from another machine, I get the same slow connection. Here are
some files from jonesy:
/etc/hosts:
127.0.0.1 localhost localhost.localdomain
192.168.1.13 jonesy.emeraldbiostructures.com jonesy
192.168.1.11 weaver.emeraldbiostructures.com weaver
192.168.1.12 ripley.emeraldbiostructures.com ripley
192.168.1.2 sapphire.emeraldbiostructures.com sapphire
192.168.1.3 kaizen.emeraldbiostructures.com kaizen
192.168.1.6 picard.emeraldbiostructures.com picard
/etc/host.conf:
order hosts,bind
multi on
/etc/hosts.allow:
#
# hosts.allow This file describes the names of the hosts which are
# allowed to use the local INET services, as decided
# by the '/usr/sbin/tcpd' server.
#
in.telnetd: LOCAL
in.ftpd: LOCAL
/etc/hosts.deny:
#
# hosts.deny This file describes the names of the hosts which are
# *not* allowed to use the local INET services, as decided
# by the '/usr/sbin/tcpd' server.
#
# The portmap line is redundant, but it is left to remind you that
# the new secure portmap uses hosts.deny and hosts.allow. In particular
# you should know that NFS uses portmap!
#ALL: ALL
These files on the other two machines looks just like these, with
appropriate changes in /etc/hosts. What could I be missing on jonesy?
Also, Chuck mentioned the possibility that the hosts files could be out
of sync. How do I check this? Thanks,
Hidong
Philippe Moutarlier wrote:
>
> It might be that the machines are trying to use DNS for connecting and
> somehow your primary DNS server doesn't work properly.
>
> Only when it times out on the first, it goes to the second which might work better.
> Once the name is resolved, things are going OK.
>
> To check that you can :
>
> - give the IP directly to the connection
>
> - add the name/IP of your local machines to /etc/hosts and make sure your
>/etc/host.conf reads:
>
> order hosts,bind
>
> - try to ping you primary DNS server.
>
> Philippe
>
> Hidong Kim <[EMAIL PROTECTED]> writes:
>
> > Hi,
> >
> > My network of three Linux Red Hat 6.0 machines has become very slow all
> > of the sudden. When I try to telnet or ftp between the machines, it
> > takes about a minute for the login prompt to come up. When it does come
> > up and I log in, working in the remote session seems to go at normal
> > speed. It seems like making that initial connection is really slow. I
> > also see this in netscape. When I launch netscape, the browser window
> > comes up quick. But then when I click a link or click to check e-mail,
> > netscape hangs for about a minute before the next window comes up.
> > After this initial slowness, things seem fine. What could be the reason
> > for this initial slowness to make network connections? Here's the
> > /etc/hosts.allow and /etc/hosts.deny for all three machines:
> >
> > #
> > # hosts.allow This file describes the names of the hosts which are
> > # allowed to use the local INET services, as decided
> > # by the '/usr/sbin/tcpd' server.
> > #
> >
> > in.telnetd :LOCAL
> > in.ftpd :LOCAL
> >
> >
> > #
> > # hosts.deny This file describes the names of the hosts which are
> > # *not* allowed to use the local INET services, as decided
> > # by the '/usr/sbin/tcpd' server.
> > #
> > # The portmap line is redundant, but it is left to remind you that
> > # the new secure portmap uses hosts.deny and hosts.allow. In particular
> > # you should know that NFS uses portmap!
> >
> > #ALL: ALL
> >
> >
> >
> > Thanks,
> >
> >
> >
> > Hidong
> >
> >
> > --
> > To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
> > as the Subject.
>
> --
> To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
> as the Subject.
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
