[comp.protocols.tcp-ip] TCP/Connect II and MultiNet

MCMAHON@TGV.COM (John 'Fast-Eddie' McMahon) (01/12/91)

The problem with MultiNet and TCP/Connect II FTP seems to be in the TCP/Connect
parser that reads the LIST FTP command back from the MultiNet server.  If you
switch the host type from "Automatic" to "Generic" when establishing the
connection it will work just fine.

John 'Fast-Eddie' McMahon    :    MCMAHON@TGV.COM    : TTTTTTTTTTTTTTTTTTTTTTTT
TGV, Incorporated            :                       :    T   GGGGGGG  V     V
603 Mission Street           : HAVK (abha) Gur bayl  :    T  G          V   V
Santa Cruz, California 95060 : bcrengvat flfgrz gb   :    T  G    GGGG   V V
408-427-4366 or 800-TGV-3440 : or qrfgeblrq ol znvy  :    T   GGGGGGG     V

mcmahon@TGV.COM (John 'Fast-Eddie' McMahon) (01/15/91)

In article <663619006.888386.MCMAHON@TGV.COM> I Wrote:
#The problem with MultiNet and TCP/Connect II FTP seems to be in the TCP/Connect
#parser that reads the LIST FTP command back from the MultiNet server.  If you
#switch the host type from "Automatic" to "Generic" when establishing the
#connection it will work just fine.

Intercon informed me that this would be fixed in Release 1.0.5 of their
software, to be released in February.

--
John 'Fast-Eddie' McMahon    :    MCMAHON@TGV.COM    : TTTTTTTTTTTTTTTTTTTTTTTT
TGV, Incorporated            :                       :    T   GGGGGGG  V     V
603 Mission Street           : HAVK (abha) Gur bayl  :    T  G          V   V
Santa Cruz, California 95060 : bcrengvat flfgrz gb   :    T  G    GGGG   V V
408-427-4366 or 800-TGV-3440 : or qrfgeblrq ol znvy  :    T   GGGGGGG     V