On 2017 Jan 15 09:41:38, you wrote to me:

 ml>> as far as Tiny's comment about multiple telnet hops, it makes sense
 ml>> because telnet can be switched in modes so that things like zmodem
 ml>> will work... that mode switch isn't transmitted up the line to the
 ml>> next telnet package because the first one ate it when it reacted to
 ml>> it... remember,

 MH> Correct, the very first telnet needs to be in binary mode for file
 MH> transfers to work.

FWIW: AFAIK, the entire telnet chain needs to be in binary mode for
tunneled file transfers to work properly...

in other words, if there's five telnet hops between the user and the remote
system, all five of those hops need to be initiated in binary mode...

what do i mean by "telnet hops"? consider that you allow users to
telnet out to other systems and those other systems also allow telnetting
out...

 MH> I'm almost certain the one that needs to be edited is the telnet from
 MH> the Mystic shuttle menu.

i have no clue how that would be done... i didn't even know mystic had a
"shuttle" menu, whatever that is...

 MH> The characters that display when you telnet from the shuttle do
 MH> include some of those single bits that configure the telnet
 MH> parameters.  We just need that "set to binary mode" sequence added.

or at least figure out how to pass those setting bits through to other
telnets further down in the chain...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin'
it wrong...
... I am so smart I can do crossword puzzles without looking at the clues.
---