ml>> i was just playing with this and cannot seem to get it to work as
 ml>> desired... i'm using the standard telnet client and the lszrz
 ml>> package... i start the download on the BBS side and then ^]!rz and
 ml>> then wait...

 PS> Can you try "^]!rz 3" and see if it makes a difference? I
 PS> just typed "^]!" on a telnet session to my firewall machine
 PS> and filedescriptor 3 ended up being connected to a socket of
 PS> some sort...

bash error: no such file: 3

or some such... then i tried &3 for both and had a bit more success but
not a real transfer as desired... the first time i saw some info but
nothing "took off" so i tried it again and this time the file did
transfer but only to the screen and not into the redirector and into rz...

the first time with &3 gives me this...

=====
Start receiging now or press  several times to abort.

telnet> !rz &3
rz waiting to receive.Retry 0: Got TIMEOUT
Retry 0: Got TIMEOUT
Retry 0: Got TIMEOUT
Retry 0: Got TIMEOUT
Retry 0: Got TIMEOUT

Transfer incomplete
*CYQ_3waldos.zip370160 7771441214 100400kq]_*CYQ_3waldos.zip370160 7771441214
100400kq]_*CYQ_3waldos.zip370160 7771441214
100400kq]_*CYQ_3waldos.zip370160 7771441214
100400kq]_*CYQ_3waldos.zip370160 7771441214
100400kq]_
No files sent

Press [ENTER] to Continue:
=====

the first line and the last two are BBS prompts... everything else was in
the telnet client and shell... almost looks like rz went too fast and then
decided the transfer was incomplete while the *CYQ stuff was the bbs trying
to sync the zmodem transfer and get started after the initial zmodem
headers...

if i had done the !rz &3 again when the CYQ stuff was
printing on the screen, the transfer would have taken place but rz would
not have been catching it... only the screen... that's what i was
describing above WRT "a bit more success"...

how did you find out that filedescriptor 3 was connected to a socket?

)\/(ark