Richard R. Kramer wrote in message <3A80888D.A0E60C44@kramer-smilko.com>…
A way this can happen is if there is an incorrect /etc/resolv.conf
file. If you don’t need to do name lookups, you can remove this file.
Otherwise, make sure the nameserver entries are correct and accessible.
And continuing this thought…
It is trying to do an inverse lookup. If your entries are correct then
- whatever DNS you are hitting doesn’t have 127.0.0.1 in the reverse
you need to ding the admin.
- If you are on private going to private you need at least dummy reverse
records to keep things fast. If going to public addresses there isn’t much
you can do.
Paul Russell wrote:
Check and see if you have extra licenses in your /.licenses file for
nodes that don’t exist.
I’ve noticed tremendous network slowdown when this is so…
Mats Pettersson <> firstname.lastname@example.org> > wrote in message
news:95po0t$fp8$> email@example.com> …
When I try to ftp (or telnet as well) to my QNX host it takes about 60
before I really get the connection.
I do the following:
ftp 127.0.0.1 (this is on my QNX-host)
and I get the following immediately:
Connected to 127.0.0.1.
60 secs later I get the login (user and password) questions.
It is more or less the same when I use telnet.
We are using Socklet if that can help.
Have anyone experienced this?
regards, Mats P