because I want to login remotely by telnet and run some programs between QNX6.3.0 . But I find the telent is very slow ,it takes me about 1 or 2minutes .can it be faster?
How do you connect to your target? Serial line? From what client system?
I think the telnet usually negotiate a whole bunch of options which can take considerable amount of time. Try playing around with the telnet options that control this. Also, if your client runs on MS Windows, try different client programs, there are plenty of them around.
Regards,
Albrecht
By the Internet , host and target both are x86 PC with qnx6.3.0. they are in the same LAN.
Thank albrecht!
I’m not with you. You say client (host??) and server (target) are in the same LAN, and still you connect via the internet? Anyway, I don’t really know what is happening because telnet between two QNX boxes in the LAN usually works very well with the default options. Have you installed SP2? I dimply remember that there was a patch for the telnetd in SP2.
Regards,
Albrecht
how can I know the vesion of telnet I used. my qnx is 6.3.0
in the terminal, use telnet like this:
#telnet 192.168.16.200
trying 192.168.16.200…
connect to 192.168.16.200
…escape ‘^]’
login:
It took about 2-3 minutes to show the above message.
It’s probably a resolver issue. Try 'telnet -N ’ on the client and
make sure the server can resolve the client.
-seanb
#telnet -N 192.168.16.200
trying 192.168.16.200…
connect to 192.168.16.200
…escape ‘^]’
login:
it is very fast to display the above three messages. but it needs 2 minutes to display " login: ". Can it be faster? Thanks !
As mentioned, it’s probably a resolver issue. You probably
have a the server set up to query a nameserver that isn’t
responding / can’t be reached. The telnetd server is probably
waiting for a reverse name lookup (gethostbyaddr()) to time
out. To test the theory, on the server try a 'ping <client_ip_addr>.
If that shows the same delay whereas 'ping -n <client_ip_addr>
doesn’t that’s further proof.
See the entry for /etc/resolv.conf under the ‘r’ section of
the utility reference. You might want to add ‘lookup file bind’
as its first line on the telnet server then add an entry for the client
in the telnet server’s /etc/hosts until you get your nameserver
sorted out.
just as you said, ping -n 192.168.16.200 is very fast to response. but ping 192.168.16.200 is very slow.
in telnet server:
/etc/resolv.conf :
#domain Berkeley.Edu
#nameserver 128.32.0.4
#nameserver 128.32.0.10
/etc/hosts:
Host Database
127.1 localhost.localdomain localhost
::1 localhost.localdomain localhost
How should I do now ? Thanks !
Hi dxwang ,
Try Putty, its a free telnet client, it works faster than native telnet and has other excellent features.
Look carefully at the /etc/resolv.conf docs. Check if you
are overriding /etc/resolv.conf with the CS_RESOLVE confstr
(getconf CS_RESOLVE).
And putty won’t help, the issue is on the server.
-seanb
in /etc/resolv.conf , there are only three sentences.
#domain Berkeley.Edu
#nameserver 128.32.0.4
#nameserver 128.32.0.10
and I can’t understand you with "Check if you
are overriding /etc/resolv.conf with the CS_RESOLVE confstr
(getconf CS_RESOLVE). " would you like to explain it for me in details . Very Thanks!
seanb: Can you explain it in detail for me , Very Thanks. now telnet ip is very very slow , telnet -n ip is a little faster . How should I change some settings . Thanks !
Type the command
getconf CS_RESOLVE
and post the result.
Make sure those nameserver IPs from the output are valid ones: accessible and can resolve your QNX hosts (reverse lookup).
Thanks everyone : I have solved it , by not using gateway and domain . now it is more fast ! 