Showing routing table, connecting to sshd takes a really long time

Showing routing table, connecting to sshd takes a really long time

Post by creamy_st » Sat, 23 Mar 2002 22:35:11



Just installed Solaris 8 on a Netra X1. The installation seemed fine,
but something isn't right with the networking.

Examples:

*When I do 'netstat -r', it takes about a minute for each entry to
appear

*When I connect to the machine using SSH, I have to wait at a blinking
cursor for a minute or so after supplying login/pass before I'm let
in.

Any Ideas?

/creamy

 
 
 

Showing routing table, connecting to sshd takes a really long time

Post by news.skynet.b » Sat, 23 Mar 2002 22:46:32


just wondering if you local dns configuration is not properly setup
this might explain the one minut wait between the operations (in fact
waiting for the request to timeout)


Quote:> Just installed Solaris 8 on a Netra X1. The installation seemed fine,
> but something isn't right with the networking.

> Examples:

> *When I do 'netstat -r', it takes about a minute for each entry to
> appear

> *When I connect to the machine using SSH, I have to wait at a blinking
> cursor for a minute or so after supplying login/pass before I'm let
> in.

> Any Ideas?

> /creamy


 
 
 

Showing routing table, connecting to sshd takes a really long time

Post by Paul Flo » Thu, 28 Mar 2002 05:46:18



Quote:>Just installed Solaris 8 on a Netra X1. The installation seemed fine,
>but something isn't right with the networking.

>Examples:

>*When I do 'netstat -r', it takes about a minute for each entry to
>appear

This is probably because it's trying to resolve the internal IP
addresses to names. If you use the -n option, it will print out the IP
addresses instead, without trying to go via the nameserver.

Quote:>*When I connect to the machine using SSH, I have to wait at a blinking
>cursor for a minute or so after supplying login/pass before I'm let
>in.

Again it's probably the same problem: name resolution. Perhaps your
/etc/resolv.conf includes more than one name server, and the first one
has problems, so after a while it switches to the second, which is
working.

You could do some tests with

nslookup host server

where host = name of host (e.g., the machine that you are connecting to
with ssh) and server = IP address of name server. If nslookup comes back
straight away, then 'server' is the right address to use. It's also
possible that the name server is badly configured.

A bientot
Paul
--
Paul Floyd                 http://paulf.free.fr (for what it's worth)

What happens if you have lead in your pants as well as lead in your pencil?

 
 
 

1. route takes long time to give the table

On Debian Testing running 2.6.7,the 'route' command is taking unusually
long time to give the table:
~# time route
Kernel IP routing table
Destination    Gateway     Genmask         Flags Metric Ref    Use Iface
x.y.z.z        *           255.255.255.255 UH    0      0        0 ppp0
192.168.1.0    *           255.255.255.0   U     0      0        0 eth0
192.168.0.0    *           255.255.255.0   U     0      0        0 eth1
default        x.y.z.z     0.0.0.0         UG    0      0        0 ppp0

real    0m20.010s
user    0m0.002s
sys     0m0.002s

However, 'route -n' command gives the output almost instantly.

Anybody else experiencing this? Any idea why this would be so?

->HS

2. Console fonts

3. netstat -p command takes a really long time to execute

4. Mouse Problems

5. EMACS takes very long time to show up after PPP has been established

6. Conlog.nlm

7. takes long time to connect via telnet.

8. Setting up imapd: how to check?

9. Why it takes a long time to connect(TCP) in this condition ?

10. route command takes a long time.

11. Telnet Takes Long Time to Connect

12. [Fwd: Re: Help: recv takes a long time to time out!]

13. Help: recv takes a long time to time out!