REALLY slow client
Erik Madsen
I'm running A/UX 3.0 on a Mac fx with an Asante Ethernet card. I connect
to this server from another Mac cx (also with an Asante card) using TCP/IP
supported by NCSA Telnet (MacTCP ver.) software.
My problem is when I connect to my server, everything on my client (the CX)
seems to go REAL slow - for example, if I do a "man cc", the man page scrolls
like it's 1200 baud or something. If I do the same command on the host
itself, it's fast and there doesn't seem to be any problem.
We have a pretty large network, but I've isolated these two machines on a
multiport box, and the same thing seems to happen. FTP transfers don't seem
to be excruciatingly slow, that I can tell, but when doing a directory of
the host, it's very slow. The same thing happens if you've got NCSA Telnet
set up on another Mac and have it available for FTP transfers (meaning just
a regular Mac, no A/UX on it or anything, set up to accept FTP from another
Mac also running NCSA Telnet).
Does this sound like a flaky driver problem, or ...? any suggestions?
Thanks
Erik
Richard Todd
>I'm running A/UX 3.0 on a Mac fx with an Asante Ethernet card. I connect
>to this server from another Mac cx (also with an Asante card) using TCP/IP
>supported by NCSA Telnet (MacTCP ver.) software.
Much the same setup as is in use at a nearby University I happen to attend:
Mac SE/30s and IIsis running NCSA Telnet w. MacTCP connecting to various
Unix hosts.
>My problem is when I connect to my server, everything on my client (the CX)
>seems to go REAL slow - for example, if I do a "man cc", the man page scrolls
>like it's 1200 baud or something. If I do the same command on the host
>itself, it's fast and there doesn't seem to be any problem.
Yeah. Happens all the time. The problem is simply that NCSA Telnet is,
without a doubt, the *slowest* terminal emulator program I've seen in my life.
Period. Even my TRS-80 Model I with my own homebrew terminal program could
put characters on the screen faster than that. Alas, NCSA Telnet is the
only freeware telnet client I know of for the Mac, so you either learn to
like slow displays or shell out the bucks for some commercial networking
package. I note that xterm displays just fine on the MacX server, and does so
with what seems like blinding speed compared to NCSA, plus it also lets you
run GhostScript and other famous X Window goodies :-).
>Does this sound like a flaky driver problem, or ...? any suggestions?
Hope that NCSA speeds up their code. As I recall, some of the earlier
releases were even slower...
--
Richard Todd rmt...@uokmax.ecn.uoknor.edu rmt...@chinet.chi.il.us
rmt...@servalan.uucp New Improved Domain: rmt...@servalan.servalan.com
"Elvis has left Bettendorf!"
Mark Boyd
macines and MACs. Perhaps you have hardware problems or configuration
problems. The NCSA software is some of the best I've seen, and I've
spent a lot of time poking around in its innards. Good code.
Mark
Trond Kandal
and employees ...
I think it is very fast and easy to use ...
Trond Kandal.
--
System-administrator: Trond Kandal, Institutt for Informatikk, Universitetet i
Trondheim AVH, N-7055 DRAGVOLL, NORWAY | e-mail: tr...@ifi.unit.no,
tro...@ifi.unit.no | voice: +47 7 59 17 26 | fax: +47 7 59 17 33
"I'm the king, I can do anything..." Jim Morrison.
Roger Hunen
>We also have the same good experince with NCSA-telnet in our site,- it is widely used by students
>and employees ...
>I think it is very fast and easy to use ...
Yes, NCSA Telnet is fast and easy to use, but....
WHEN I TRY TO DO FTP OVER A ROUTER WHICH INTERFACES MY ETHERNET TO
A 64 KBIT/SEC LEASED LINE, NCSA TELNET MESSES UP THE LINE. IT DOES
NOT PROCESS 'ICMP SOURCE QUENCH' MESSAGES AND THE TCP FLOW CONTROL
IS APPARENTLY BROKEN.
I hate to say this: NCSA is fine on ethernet where a PC can hardly flood
the receiving host. But when I get a congested WAN router because the
flow control is broken, I better not run the risk that my colleagues kill
me...
Regards,
-Roger
(no fancy signature yet, usual disclaimers apply)