[comp.protocols.tcp-ip.ibmpc] NCSA Telnet and FTP to VAX/VMS

Salvatore Saieva <SLVQC@CUNYVM> (03/20/90)

I've been using NCSA FTP between PC's on our thin wire
ethernet LAN flawlessly. However, things are not so good
using Telnet or FTP to our VAX/VMS system. Sometimes NCSA
Telnet and FTP can initiate a connection, sometimes it can't.
When a connection to the VAX is negotiated, it is unreliable,
slow, and choppy; records are received in small pieces with
long delays between the separate pieces and what I type is also
echoed in the same ``choppy'' manner.

On the PC side I'm using the NE1000 and WD8003E packet
drivers from the Clarkson driver collection for the appropriate
ethernet cards. We're also running Novell Advanced Netware V2.15
over the thin wire ethernet (if it matters) and I never have the
Clarkson drivers and the Netware drivers loaded at the same time.
I have experimented with the various parameters in the config.tel
file but I haven't seen any improvements.

On the VAX side (an 8600 and a 785) we're running Wollongong
TCP/IP and FTP software. The thin wire ethernet is connected
to the VAX's ethernet through a Delni box.

Does anyone have any clues as to why this isn't working?
I've been trying to get this working for some time now but
I haven't had too much luck going to our VAX's. Are there
special settings for the parameters in the config.tel file?
A special setup on the VMS side? Is it even feasible given
our environment and connections? Any information would be
very appreciated.

Salvatore Saieva
Queens College, N.Y.
Academic Computer Center