I found out that the initial slowing is caused by a bad wire. Now it’s
fixed. Yet, the problem switch to the slowing of inital connection to
telnet/ftp. You ask me to post a sin, do you think that the priority would
have contributed in this problem?
It’s the traffic that’s slow, not the initial connection to telnet/ftp -
at
least that is my understanding.
My understanding is:
- /etc/resolv.conf removal was a red herring, it has nothing to do with
the problem (unless it’s a connection time issue, which it isn’t).
- For some reason ftp/telnet seem to experience sluggish behaviour, but
phindows does not.
Does this sluggish behaviour occur from all windows boxes? Does it occur
if
you’re ftping from the QNX4 box out to another box? If you have another
QNX4 node on the network, do transfers between QNX4 nodes via FLEET or ftp
also seem sluggish. Has anything been added to your network from the last
time things worked properly? Have you checked your network to see if
someone is using the same IP address by accident?
Please post a sin and a ser ver of your QNX4 system.
–
Cheers,
Adam
QNX Software Systems Ltd.
[ > amallory@qnx.com > ]
With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <> pschon@baste.magibox.net
Xiaodan Tang <> xtang@qnx.com> > wrote in message
news:aslg6h$qs2$> 1@nntp.qnx.com> …
OK, maybe I should re-explain, so you can decided what to do…
The problem you are seeing, telnet/ftp into a QNX4 box need to wait
“minutes” to get a prompt, is cause by:
When telnetd/ftpd on QNX4 started to response the incomming request,
they usually need to do a “reverse name lookup” on the request. That is,
they look at the request, knowing which IP it is come from, and then
try to resolve the IP into a hostname.
How to resolve an IP into a hostname, is based on how name resolver
works. It either check the /etc/resolv.conf and ask the nameserver; or
it looks into /etc/hosts to see if there is a match. Should it look in
to
the
/etc/hosts first, or should it talk to a nameserver first, is controled
by
the
"lookup " keyword in /etc/resolv.conf (check menu for that). By default,
it goes to nameserver first.
Now the typical causing of your satuation is, you set up the
/etc/resolv.conf,
the telnetd/ftpd will then take your window BOX’s IP to the nameserver.
AND the nameserver if not properly setup for reverse resolving (a ip
to a name). It takes “minutes” for telnetd/ftpd realize the nameserver
is
not going to answer, and timeout, and go check /etc/hosts, and then give
up the resolve, goes ahead to services you.
By remove the /etc/resolv.conf, telnetd/ftpd will notice they don’t have
a
nameserver to talk to, and go check /etc/hosts, and give up immediatly,
which makes you “fell” the problem is solved.
However, you noticed this is not the proper way to manage a QNX box
in a big network. Like phindows may not works, “ping yahoo.com” from
the QNX box probably not going to work, because it can’t resolve the
name anymore …
If you have the control of the nameserver, fix it so it can do reverse
resolve properly. Otherwise, your chance is put “lookup file bind”
in /etc/resolv.conf, the resolver will look into /etc/hosts FIRST,
and you put all those windows’ box into your /etc/hosts, so that
the resolver can reverse resolve through the /etc/hosts, and no
need to goto nameserver.
Hopefully this explained everything…
-xtang
Seddrak <> qdn.public.qnx4@inn.qnx.com> > wrote in message
news:asleju$5lf$> 1@inn.qnx.com> …
Hi:
The problem is after removing /etc/resolv.conf, yes the speed when
accessing
QNX4 using window via telnet and ftp is faster, but phindow doesn’t
work
anymore. Currently we have set up so that QNX 4 will act as server,
and
our
goal is any computer can access to this server in any university
campus
location. We want all telnet, ftp, and phindow to be able to access
QNX
4
from window without any sluggish problem. The sluggish in the
trasnfer
rate, for some reason, only occurs to ftp and telnet and not phindow
(this
is when /etc/resolv.conf is NOT removed). As a result, is there any
way
to
increase the speed of telnet and ftp with taking the line out and that
all
telnet, ftp and phindow will work fine? Thanks,
Seddrak
“Adam Mallory” <> amallory@qnx.com> > wrote in message
news:asl7mk$lkc$> 1@nntp.qnx.com> …
Removing /etc/resolv.conf should not have any effect on transfer
speed,
only
initial connection establishment. Have you tried connecting the
Windows
and
QNX4 box via cross over cable? See if that results in any transfer
speed
change.
-Adam
Seddrak <> qdn.public.qnx4@inn.qnx.com> > wrote in message
news:asb47p$fni$> 1@inn.qnx.com> …
It is the transfer speed that is having a problem. Phindow is
working
fine
while telnet and ftp are working slowly. When telnet or ftp, we
did
not
open phindow, so it doesn’t matter, right? or is there some
command
we
need
to set in phindow? thanks.
seddrak’
“Adam Mallory” <> amallory@qnx.com> > wrote in message
news:as8mqu$1da$> 1@nntp.qnx.com> …
You’ll have to be more specific about “sluggish”. What is
sluggish
about
ftp or telnet? Is it the login/connect time? If so, this is
probably
a
reverse nameserver resolving issue (ie. the nameserver the qnx4
box
thinks
it needs to use has a route, but isn’t on the network/not
responding).
If
it’s just transfer speed, then something else is the problem.
Is
the
phindows session idle (ie. not redrawing anything etc), when
you’re
doing
ftp/telnet.
–
Cheers,
Adam
QNX Software Systems Ltd.
[ > amallory@qnx.com > ]
With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <> pschon@baste.magibox.net
Seddrak Luu <> qdn.public.qnx4@inn.qnx.com> > wrote in message
news:as8kk1$nt2$> 1@inn.qnx.com> …
The big picture is:
I have a computer running in QNX 4.25 and working as a server.
Another
computer running window 2000 installed phindow, ftp and
telnet.
Before
removing /etc/resolv.conf, accessing the server via phindow is
fine,
but
accessing via ftp and telnet is extremely slow. I was
wondering
if
there
are some ways to improve the system so that all three
accessing
equipment
will run smoothly without any sluggish problem.
Thanks,
Seddrak
“Adam Mallory” <> amallory@qnx.com> > wrote in message
news:as8a5a$npc$> 1@nntp.qnx.com> …
You can put host IP mappings in your /etc/hosts file, but
some
applications
will want to do a reverse lookup, and that will take a while
to
timeout.
What was the original problem before you removed
/etc/resolv.conf -
perhaps
there are better ways of solving or working around the
original
issue.
–
Cheers,
Adam
QNX Software Systems Ltd.
[ > amallory@qnx.com > ]
With a PC, I always felt limited by the software
available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <> pschon@baste.magibox.net
Seddrak Luu <> qdn.public.qnx4@inn.qnx.com> > wrote in message
news:as86od$a4s$> 1@inn.qnx.com> …
Hi:
Someone suggested to remove the line. Since I am not
familiar
with
this
suggest, I did that. Anyways, so is there anyway to
decrease
the
timeout
to
improve the sluggish problem?
Seddrak
“Adam Mallory” <> amallory@qnx.com> > wrote in message
news:as7s3q$f7t$> 1@nntp.qnx.com> …
Why did you remove the /etc/resolv.conf file? The
sluggishness
is
probably
due to the requirement to timeout on every DNS name
lookup
(since
you’ve
just removed the file that says how to do it).
-Adam
Seddrak Luu <> qdn.public.qnx4@inn.qnx.com> > wrote in
message
news:as6v1u$q5t$> 1@inn.qnx.com> …
after I rm -f/etc/resolv.conf, telnet and ftp do work,
but
phindow
doesn’t.
Is there a way such that all phindow, telnet and ftp
will
work
perfectly
without the sluggish problem?
“Frank Liu” <> liug@mama.indstate.edu> > wrote in message
news:antooi$h6b$> 1@inn.qnx.com> …
rm -f /etc/resolv.conf
on the qnx box and you are set.
frank
Seddrak Luu <> qdn.public.qnx4@inn.qnx.com> > wrote:
Currently, I have:
Host Database
This file should contain the addresses and
aliases
for local hosts that share this file.
It is used only for “ifconfig” and other
operations
before the nameserver is started.
127.1 localhost localhost.my.domain
Imaginary network.
#10.2 myname.my.domain myname
#10.3 myfriend.my.domain myfriend
192.168.0.3 qnxnet1.ensc.sfu.ca qnxnet1
Do you mean uncomment the line 10.2 and 10.3? If
not,
what
entry
is
needed?
Thanks for your help.
“Paul Vander Byl” <> paul@gandacar.ca> > wrote in
message
news:ans0p5$90p$> 1@inn.qnx.com> …
You need to have the DNS working or an entry in
the
hosts
file
so
it
doesn’t
need to wait to timeout.
“Seddrak Luu” <> qdn.public.qnx4@inn.qnx.com> > wrote
in
message
news:anpq93$l7j$> 2@inn.qnx.com> …
Hi:
I have connected a computer and the labtop with
a
hub.
The
computer
is
running on win2000 and the labtop is running
QNX
4.25.
When
the
comptuer
accessing labtop, it runs just fine. But when
it
wants
to
access
telnet
and
FTP, it is sluggish and I need to wait for
minutes
in
order
for
it
to
connect. Can you suggest a way to fix this?
Thanks.
Seddrak
\