rds95@leah.Albany.Edu (Robert Seals) (06/01/89)
Well, ncsa telnet is sure neato, but I am having one real big problem. I am unable to transfer certain files from the remote machine to my PC. I can send from the PC to the remote machine, and it seems that small files will go back, but usually, it says "150 Opening connection\n" and then sits there doing nothing. File transfer is enabled, and the standalone ftp did the same kind of thing. My machine is a 386 with the WD8003; the remote machine is a uVaxII with Ultrix 1.2. (I just tested the same thing connected to a Unisys 7000 (CCI 6/32) with 4.3-tahoe, and it worked. Darn. Well, does this mean that Ultrix is the stinker?) rob
rk@lexicon.com (Bob Kukura) (06/01/89)
In article <1869@leah.Albany.Edu> rds95@leah.Albany.Edu (Robert Seals) writes: > Well, ncsa telnet is sure neato, but I am having one real big > problem. I am unable to transfer certain files from the remote machine > to my PC. I can send from the PC to the remote machine, and it seems > that small files will go back, but usually, it says "150 Opening > connection\n" and then sits there doing nothing. File transfer is > enabled, and the standalone ftp did the same kind of > thing. My machine is a 386 with the WD8003; the remote machine is > a uVaxII with Ultrix 1.2. > > (I just tested the same thing connected to a Unisys 7000 (CCI 6/32) with > 4.3-tahoe, and it worked. Darn. Well, does this mean that Ultrix is the > stinker?) > > rob We had a problem with very similar symptoms using PC-NFS with Ultrix. Very small telnet and ftp transfers worked fine, but larger ones failed. Ultrix uses trailer encapsulation, which moves the variable-sized packet header data to the end of the packet so that the received packet data is page-aligned can be mapped into the user address space without having to copy it. PC-NFS could not handle trailer encapsulated packets, which Ultrix apparently only generated when doing transfers larger that about 1.5 K. The solution was to edit the -trailers option into the /etc/ifconfig line in the rc.local file on each Ultrix system to disable trailer encapsulation. This is no longer necessary as of Ultrix V3.0, which negotiates with each host on whether to use trailer encapsulation. -- -Bob Kukura smart: rk@lexicon.com dumb: {husc6,linus,harvard,bbn}!spdcc!lexicon!rk phone: (617) 891-6790
shoat@cs.glasgow.ac.uk (Mr. David Shoat) (06/02/89)
I've been trying out a couple of telnet implementations recently and have had problems with both. The first is NCSA telnet on a Mac SE with a Kinetics etherport. The second is the version of telnet supplied with PC-NFS V3.0. The hosts are microvaxen running Ultrix (V2.0 and V2.3). Everything is on ethernet with class-a addressing. In both cases, telnet will eventually hang. This usually happens when running something which uses screen-addressing in vt100 mode. I haven't had the patience to see if it recovers - it takes a lot longer than 11 seconds. It looks like Ultrix may be at fault here, although telnet works fine between the vaxes. Anyone else had this type of problem? David Shoat Department of Medical Cardiology Glasgow Royal Infirmary.