Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!usc!elroy.jpl.nasa.gov!jarthur!bridge2!api!gpz From: gpz@ESD.3Com.COM (G. Paul Ziemba) Newsgroups: comp.protocols.tcp-ip Subject: Re: Problem with Xmodem and 3Com terminal server Message-ID: Date: 1 Nov 90 19:11:20 GMT References: <9010312149.AA07742@z.nsf.gov> <12634372337.2.BILLW@mathom.cisco.com> Sender: news@bridge2.ESD.3Com.COM Lines: 32 BILLW@MATHOM.CISCO.COM (William Chops Westfield) writes: >Even when transferring text files, XMODEM needs a clear 8-bit path to >accomadate its block counts and checksum. By definition, telnet is a >7 bit protocol, and you must negotiate "binary" mode to get an 8-bit >path. The terminal server may be refusing binary mode negotiations, >may just do binary incorrectly, or may just need configured differently. Unfortunately, I did not read the original query, so I'm guessing that the original poster (someone @z.nsf.gov) is trying to establish an 8-bit path from a 3com terminal server. This can be done...the following settings are needed: fcf=n flow-control-from disabled fct=n flow-control-to disabled bra=ig break-action ignore ecmc=d escape-cmd-char disabled depending on the comserver software version, you may also need to set xb=on transmit binary enabled lbra=l local-break-action listen (so you can break the connection locally) If that doesn't answer the original question, well, then, never mind :-) ~!paul -- Paul Ziemba api!gpz gpz@ESD.3com.com 408.764.5390 OS/2: just say no. "How much char could a char star star if char star could star char?" (quote stolen from mspercy@clemson.clemson.edu)