Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!OMNIGATE.CLARKSON.EDU!bkc
From: bkc@OMNIGATE.CLARKSON.EDU (Brad Clements)
Newsgroups: comp.protocols.tcp-ip
Subject: Re:  ncsa telnet (pc) ftp bug ?
Message-ID: <8905272015.AA16146@ucbvax.Berkeley.EDU>
Date: 27 May 89 18:39:56 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 24

What version of ftpbin and telbin are you using?

We had a similar problem here, using telbin to connect to a vax 3500 running
cmu-tek-tcp.  The problem showed up when users went to change their passwords.
The would get "invalid password" or something like that when entering the
new password. Turns out that cmu-tcp was negotiating BINARY telnet option, the
PC says 'ya, sure' but then didn't correctly implement binary EOL syntax.

The quickest fix we came up with is for telbin to say 'no binary mode' unless
connected to a 3270 type machine. (So, version 2.2C is broken, and tries binary
mode, and 2.2D says no to binary mode, but if it said yes, it'd still
be broken).

Ftpbin strips off incoming telnet options and discards them. Perhaps
(I have no idea why this would happen) your vax is sending a DO Binary option on
the ftp control channel. If the PC ignores it, and never answers,
what does the vax do?

The CRNUL option only effects what is sent to a host system when <RETURN> is pressed
on the PC keyboard while using telbin or tn3270. (2.2TN).


| Brad Clements          bkc@omnigate.clarkson.edu        bkc@clgw.bitnet 
| Network Engineer       Clarkson University              (315)268-2292